You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Mark Payne (JIRA)" <ji...@apache.org> on 2016/11/16 15:17:58 UTC
[jira] [Commented] (NIFI-2868)
nifi.flowcontroller.autoResumeState=false does not work when NiFi is
clustered
[ https://issues.apache.org/jira/browse/NIFI-2868?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15670672#comment-15670672 ]
Mark Payne commented on NIFI-2868:
----------------------------------
[~msclarke] - I am trying to replicate this on the current master branch (1.1.0-SNAPSHOT) but am not able to replicate. Are you still seeing this issue?
> nifi.flowcontroller.autoResumeState=false does not work when NiFi is clustered
> ------------------------------------------------------------------------------
>
> Key: NIFI-2868
> URL: https://issues.apache.org/jira/browse/NIFI-2868
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
> Affects Versions: 1.0.0
> Environment: Centos 7
> Reporter: Matthew Clarke
> Fix For: 1.2.0
>
>
> In a NiFi clustered environment it is not possible to change the nifi.flowcontroller.autoResumeState= nifi property from true to false in order to bring up flow in a completely stopped state.
> This property only seems to work for standalone instances.
> While the nodes do come up with all processors in a stop state initially, as soon as Election completes, previously running processors are started.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)