[
https://issues.apache.org/jira/browse/NIFI-8970?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17405225#comment-17405225
]
Mark Payne commented on NIFI-8970:
----------------------------------
This appears to be working as designed. If the node that data is being sent to
is not available, data will queue up and wait for the node to come back.
Otherwise, you can end up in problematic situations in which some of the data
is sent to the node, and then it has problems and the rest is sent to another
node, and that defeats the purpose of single-node load balancing strategy. If
the node is removed from the cluster, a new "Single Node" will be chosen and
data will begin flowing to that one. But as long as the node is part of the
cluster, it will queue up and wait for that node to come back.
> 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 single 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 single node will not come back till the node comes back up, but
> should/does a new single need to be selected when the current single node is
> not working?
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
