[
https://issues.apache.org/jira/browse/NIFI-11450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17948934#comment-17948934
]
Nissim Shiman commented on NIFI-11450:
--------------------------------------
This issue is still the case on 2.4.0.
Set up three node cluster with single processor running.
On one node, set nifi.flowcontroller.autoResumeState to be false
*1.* If that node is stopped, flow.json.gz removed, and node started, processor
will be in ENABLED state on this node only. (and will remain RUNNING on other
nodes)
This is the case of this ticket.
*2.* If, instead, node was restarted (i.e. keeping flow.json.gz), processor
will usually also be in ENABLED state on this node only, but sometimes will be
RUNNING (i.e. even with local setting of autoResumeState of false).
About 70% of the time it will be ENABLED on the restart.
On the other nodes it will remain RUNNING
*3.* If, instead, node is disconnected and reconnected (via gui), the processor
will be in the RUNNING state (i.e. it will ignore local setting of
autoResumeState of false).
*4.* In a worse case scenerio, if the node with autoResumeState with false
comes up with its Processors as ENABLED and then becomes the primary node and
the other nodes are disconnected/reconnected
then processors will be ENABLED on all nodes of the cluster, despite
autoResumeState being true on all but one node.
All of these cases are edge cases as users should set
nifi.flowcontroller.autoResumeState consistently on all nodes, but what should
behavior be if they are not the same?
[~markap14] and/or [~exceptionfactory] Would you have any thoughts where
nifi.flowcontroller.autoResumeState is not the set the same on all nodes?
> Node respecting nifi.flowcontroller.autoResumeState when joining cluster
> ------------------------------------------------------------------------
>
> Key: NIFI-11450
> URL: https://issues.apache.org/jira/browse/NIFI-11450
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
> Affects Versions: 1.19.1
> Environment: Nifi version 1.19.1. Linux. JDK11+
> Reporter: Phil Lord
> Assignee: Nissim Shiman
> Priority: Critical
>
> Mistakenly tried to connect a node to an active cluster that had the
> following setting: nifi.flowcontroller.autoResumeState=true .
> The flow.xml/json were both removed completely prior to attempting to connect
> node to the cluster, then started the node. The node connected to the
> cluster without issue, however all components/controllerServices on that node
> were in a stopped state(due to the property mentioned above).
> Is this correct behavior given that the flow that was inherited from the
> cluster had components started/etc. I would think the node should either
> fail to join the cluster/start?
> This was running Nifi 1.19.1... unclear if it's resolved in latest release.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
