[
https://issues.apache.org/jira/browse/NIFI-1301?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthew Clarke updated NIFI-1301:
---------------------------------
Attachment: dumpRPGHang.log
I have attached a NiFi dump log produced while the NiFi instance was hung due
to the RPG running thread.
> RPG can become hung when input port on target NiFi does not accept files
> because of backpressure
> ------------------------------------------------------------------------------------------------
>
> Key: NIFI-1301
> URL: https://issues.apache.org/jira/browse/NIFI-1301
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
> Affects Versions: 0.4.0
> Reporter: Matthew Clarke
> Attachments: dumpRPGHang.log
>
>
> If i have an RPG sending to a input port on another NiFi and that input port
> is no longer accepting files because of backpressure on the input port
> connection, the sending NiFi starts logging that the destination port is full.
> The potential problem is that it create a log message for every file that is
> queueing up on the connection(s) feeding that RPG destination input port.
> This logging seems excess.
>
> The critical issue:
> Also when i select "disable transmission" I get the spinning wheel but thread
> does not complete. Entire instance is now unresponsive.
> Even though it became hung on request to disable transmission, on restart it
> started running again. Hung again.
> The only options for regaining control is to either restart with auto resume
> state set to false or take back pressure off destination input port so thread
> can complete.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
