I deployed a MiNiFi on an edge device and send the message to remote process 
group, MiNiFi Binlog input port. As the picture described:


I stop the JoltTransformJSON , after the queue is full, the MiNiFi still 
processes and then OutOfMemory.  
Althoug I  restart the JoltTransformJSON  again and the queue becomes zero, the 
MiNiFi processes hangs and not process again.

2019-07-26 19:34:11,071 WARN [Timer-Driven Process Thread-3] 
o.a.nifi.remote.client.http.HttpClient Penalizing a peer 
Peer[url=http://10.44.51.33:8080/nifi-api] due to java.io.IOException: 
Unexpected response code: 503 errCode:Port's Destination is Full 
errMessage:Received port identifier 18c0bff2-016c-1000-ffff-ffffe3eb065c, but 
its destination is full
2019-07-26 19:34:11,071 INFO [Timer-Driven Process Thread-3] 
o.a.nifi.remote.client.http.HttpClient Couldn't find a valid peer to 
communicate with.
2019-07-26 19:34:11,071 ERROR [Timer-Driven Process Thread-10] 
org.apache.nifi.minifi.MiNiFi An Unknown Error Occurred in Thread 
Thread[Timer-Driven Process Thread-10,5,main]: java.lang.OutOfMemoryError: GC 
overhead limit exceeded

Does Nifi support backpressure between different nifi instances? 
If not, how can i implement this function?   




[email protected]

Reply via email to