[
https://issues.apache.org/jira/browse/NIFI-878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15856189#comment-15856189
]
Matt Gilman commented on NIFI-878:
----------------------------------
[~trixpan] I don't know that it has. Obviously, the NCM portion of this
description is OBE but the general issue when (re)joining probably should
evaluated.
I believe it semi-related to another JIRA [1] which was created to re-evaluate
which fields are used when determining flow inheritability to ensure consistent
configuration throughout the cluster.
[1] https://issues.apache.org/jira/browse/NIFI-1963
> Ensure consistent component state throughout a cluster
> ------------------------------------------------------
>
> Key: NIFI-878
> URL: https://issues.apache.org/jira/browse/NIFI-878
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
> Reporter: Matt Gilman
>
> When clustered, the NCM will relay the autoResumeState flag to the nodes that
> join. If this flag is set to false, when a node joins it will not
> automatically start the flow. If the user had made made flow changes and
> started components, this could lead to inconsistent running states.
> Need to ensure that the running state remains consistent throughout the
> cluster regardless of the value of autoResumeState and changes that the user
> has made to the flow.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
