[
https://issues.apache.org/jira/browse/NIFI-14576?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nissim Shiman updated NIFI-14576:
---------------------------------
Description:
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
always remained RUNNING)
On clustered NiFi, processor will *not* be running. (in flow.json.gz
scheduledState was modified to and remains ENABLED)
Which is the desired state of the processor?
was:
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?
> 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
> Affects Versions: 1.24.0, 2.4.0
> Reporter: Nissim Shiman
> Priority: Major
>
> 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 always remained RUNNING)
> On clustered NiFi, processor will *not* be running. (in flow.json.gz
> scheduledState was modified to and remains ENABLED)
> Which is the desired state of the processor?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
