[
https://issues.apache.org/jira/browse/NIFI-1997?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15325116#comment-15325116
]
ASF GitHub Bot commented on NIFI-1997:
--------------------------------------
GitHub user markap14 opened a pull request:
https://github.com/apache/nifi/pull/520
NIFI-1997: Use the 'autoResumeState' property defined in nifi.properties on
each node instead of inheriting the property from the Cluster Coordinator
Use the 'autoResumeState' property defined in nifi.properties on each node
instead of inheriting the property from the Cluster Coordinator
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/markap14/nifi NIFI-1997
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/nifi/pull/520.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #520
----
commit 8cebe78d8e93694bce847c3e3c38802aa4f701eb
Author: Mark Payne <[email protected]>
Date: 2016-06-10T18:35:47Z
NIFI-1996: Fixed bug in the generation of UUID's for components when
dealing with Snippets
commit 4f997585c3ff4c3997f76f0183ee234032d23251
Author: Mark Payne <[email protected]>
Date: 2016-06-10T19:16:18Z
NIFI-1997: Use the 'autoResumeState' property defined in nifi.properties on
each node instead of inheriting the property from the Cluster Coordinator
----
> On restart, a node that joins cluster does not update processors' run state
> to match the cluster
> ------------------------------------------------------------------------------------------------
>
> Key: NIFI-1997
> URL: https://issues.apache.org/jira/browse/NIFI-1997
> Project: Apache NiFi
> Issue Type: Bug
> Affects Versions: 1.0.0
> Reporter: Mark Payne
> Assignee: Mark Payne
> Priority: Blocker
> Fix For: 1.0.0
>
>
> If I have a cluster, I can disconnect a node from the cluster and stop a
> Processor. If I then re-join the node to the cluster, it will start running
> the processor again, as it should.
> However, if I disconnect a node from the cluster and stop a Processor, and
> then restart that node instead of joining it back into the cluster, the
> problem arises. The node restarts and joins the cluster successfully but does
> not start the Processor that is currently stopped.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
