[
https://issues.apache.org/jira/browse/NIFI-9574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17476663#comment-17476663
]
Mahieddine Cherif commented on NIFI-9574:
-----------------------------------------
[~markap14] thank you for you analysis, i must confess that we are pushing our
NiFi cluster to the limit on our small setup especially regarding the CPU
usage, regarding the heap we basically dont load content into attributes (thats
forbidden by our guidelines), i must also admit that even when our nifi cluster
doesn't process anything (we have a kind of free window when no dataflow run),
the heap usage is still high, i guess we simply need more heap or maybe exclude
some processors from our instance (im exploring that possibility) or both.
All in all after some digging there was a dataflow that was running too much in
comparison of normal days (due to a remote system that was abnormally sending
too much data) and magically when the usage went down the error went away,
thanks a lot for your answer i didn't link before between the error we had and
resource saturation that we are experiencing (which is now obvious).
> 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
> Attachments: Screenshot 2022-01-14 at 19.21.11.png, Screenshot
> 2022-01-14 at 19.21.16.png, Screenshot 2022-01-14 at 19.21.36.png, Screenshot
> 2022-01-14 at 19.21.46.png
>
>
> 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)
