You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@nifi.apache.org by "Phil Lord (Jira)" <ji...@apache.org> on 2023/04/14 16:40:00 UTC

[jira] [Updated] (NIFI-11450) Node respecting nifi.flowcontroller.autoResumeState when joining cluster

     [ https://issues.apache.org/jira/browse/NIFI-11450?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Phil Lord updated NIFI-11450:
-----------------------------
    Environment: Nifi version 1.19.1.  Linux.  JDK11+  (was: Nifi version 11.  Linux.  JDK11+)

> 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
>            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)