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

Posted to issues@nifi.apache.org by "Nissim Shiman (Jira)" <ji...@apache.org> on 2025/05/16 16:35:00 UTC

[jira] [Created] (NIFI-14576) nifi.flowcontroller.autoResumeState set to false behaves differently if NiFi runs standalone or as cluster

Nissim Shiman created NIFI-14576:
------------------------------------

             Summary: nifi.flowcontroller.autoResumeState set to false behaves differently if NiFi runs standalone or as cluster
                 Key: NIFI-14576
                 URL: https://issues.apache.org/jira/browse/NIFI-14576
             Project: Apache NiFi
          Issue Type: Bug
            Reporter: Nissim Shiman


Run NiFi, (both as a standalone or as cluster), with a processor running, and shutdown.

Set nifi.flowcontroller.autoResumeState to false (on each of the nodes, if using cluster) and start.

Processor will not be running (as expected).  This is the same when running standalone or as a cluster.

Shutdown NiFi(s) and set nifi.flowcontroller.autoResumeState to true (on each of the nodes, if using cluster) and start.

On standalone NiFi, processor will be running. (in flow.json.gz scheduledState remained/remains RUNNING) 

On clustered NiFi, processor will *not* be running.  (in flow.json.gz scheduledState is now ENABLED)

Which is the desired state of the processor?



--
This message was sent by Atlassian Jira
(v8.20.10#820010)