[
https://issues.apache.org/jira/browse/NIFI-11450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17952294#comment-17952294
]
ASF subversion and git services commented on NIFI-11450:
--------------------------------------------------------
Commit 4b9da2a01de1e9d818244c0b7d2e8aed57bba92c in nifi's branch
refs/heads/main from NissimShiman
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=4b9da2a01d ]
NIFI-11450 Added documentation for autoResumeState property (#9955)
Signed-off-by: David Handermann <[email protected]>
> 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
> Time Spent: 20m
> Remaining Estimate: 0h
>
> 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)
