[
https://issues.apache.org/jira/browse/NIFI-8970?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kevin J O'Connor updated NIFI-8970:
-----------------------------------
Description: When running a NiFi cluster and one of the NiFi nodes stop
working (I assume this is the node NiFi is assigning work to as the standalone
node). The FlowFiles in a queue with load balance strategy single node will be
infinitely actively balancing. It seems as though new work is still being
assigned to the node that is not working. I get the current work assigned to
the standalone node will not come back till the node comes back up, but
should/does a new standalone need to be selected when the current standalone
node is not working? (was: When running a NiFi cluster and one of the NiFi
nodes stop working (I assume this is the node NiFi is assigning work to as the
standalone node). The FlowFiles in a queue with load balance strategy single
node will be infinitely actively balancing. It seems as though new work is
still being assigned to the node that is not working. I get the current work
assigned to the standalone node will not come back till the node comes back up,
but should/does a new standalone be selected when the current standalone node
is not working?)
> NiFi FlowFiles stuck in queue when using Single Node load balance strategy
> --------------------------------------------------------------------------
>
> Key: NIFI-8970
> URL: https://issues.apache.org/jira/browse/NIFI-8970
> Project: Apache NiFi
> Issue Type: Bug
> Affects Versions: 1.12.1
> Reporter: Kevin J O'Connor
> Priority: Critical
>
> When running a NiFi cluster and one of the NiFi nodes stop working (I assume
> this is the node NiFi is assigning work to as the standalone node). The
> FlowFiles in a queue with load balance strategy single node will be
> infinitely actively balancing. It seems as though new work is still being
> assigned to the node that is not working. I get the current work assigned to
> the standalone node will not come back till the node comes back up, but
> should/does a new standalone need to be selected when the current standalone
> node is not working?
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
