[ 
https://issues.apache.org/jira/browse/NIFI-9574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17476167#comment-17476167
 ] 

Mark Payne edited comment on NIFI-9574 at 1/14/22, 3:10 PM:
------------------------------------------------------------

Sounds like the "sending node" timed out when sending the data. How many nodes 
are in the cluster? What values do you have set in {{nifi.properties}} for 
{{nifi.cluster.load.balance.connections.per.node,}} 
{{{}nifi.cluster.load.balance.max.thread.count and 
{{nifi.cluster.load.balance.comms.timeout}}? You said you migrated to 1.15.2.  
What version were you running before that?


was (Author: markap14):
Sounds like the "sending node" timed out when sending the data. How many nodes 
are in the cluster? What values do you have set in {{nifi.properties}} for 
{{nifi.cluster.load.balance.connections.per.node,}} 
{{{}nifi.cluster.load.balance.max.thread.count and 
{{nifi.cluster.load.balance.comms.timeout}}{}}}? You said you migrated to 
1.15.2.  What version were you running before that?

>  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)

Reply via email to