[
https://issues.apache.org/jira/browse/NIFI-9574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17476199#comment-17476199
]
Mark Payne commented on NIFI-9574:
----------------------------------
[~mahieddine] I wouldn't recommend running nifi on a 2-core VM. At the absolute
minimum I'd use 4, preferably 8+ cores.
I'd also look for other errors in the logs. How healthy is the heap? How large
is it? How much garbage collection is occurring? Given that it sounds like it's
timing out, I'd be concerned with what else is happening that's causing the
nodes not to communicate well.
> Failed to decrypt data from Peer
> ---------------------------------
>
> Key: NIFI-9574
> URL: https://issues.apache.org/jira/browse/NIFI-9574
> Project: Apache NiFi
> Issue Type: Bug
> Reporter: Mahieddine Cherif
> Priority: Major
>
> After a migration to 1.15.2 it seems like we have almost systematically this
> error on our cluster all the time
> {code:java}
> Failed to communicate with Peer
> nifi-0.nifi-headless.apache-nifi.svc.cluster.local:8443 when load balancing
> data for Connection with ID b76e7297-e8a0-3b2b-ba30-d338db411301 due to
> java.io.IOException: Failed to decrypt data from Peer
> nifi-0.nifi-headless.apache-nifi.svc.cluster.local:8443 because Peer
> unexpectedly closed connection
> {code}
> Files get stuck in the queue mentioned, it's not always the same, these are
> simple round robin queues with or without compression.
> When we recreate the cluster it goes for like some time and then it occurs
> again and again
> Is there a particular reason ?
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
