Hello, This is not something that should be occurring, so it's difficult to say how to avoid the problem. I have a few questions to help understand the scenario better.
What version of NiFi is the sending side running? Is the remote instance a single NiFi instance or a cluster? When you start seeing OutOfMemoryError, how many FlowFiles are queued up waiting to be sent? Do the FlowFiles to be sent have lots of attributes or any really large attributes? Is the Remote Process Group configured to send data via "Raw Socket" or HTTP protocol? (this can be determined by right clicking on the Remote Process Group and going to Configure) How large is the NiFi heap? (set in conf/bootstrap.conf, as the -Xms and -Xmx parameters) Thanks -Mark On Jul 27, 2019, at 9:09 AM, [email protected]<mailto:[email protected]> wrote: A processor send message to a remote process group。 If the remote process group crash or blocked， after some time the local nifi instance will throw OutOfMemoryError and hanged to die. How can i avoid the Dying of the local Nifi instance? ________________________________ [email protected]<mailto:[email protected]>
