[
https://issues.apache.org/jira/browse/NIFI-2316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15384668#comment-15384668
]
ASF GitHub Bot commented on NIFI-2316:
--------------------------------------
GitHub user markap14 opened a pull request:
https://github.com/apache/nifi/pull/678
NIFI-2316, NIFI-2318: Ensure that we do not save the flow before init…
…ializing the Run Status of components. Clarify the Node Event messages
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/markap14/nifi NIFI-2316
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/nifi/pull/678.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 #678
----
commit d728aa7e4022a70f6aff6b4bfb1184a24f357755
Author: Mark Payne <[email protected]>
Date: 2016-07-19T18:49:38Z
NIFI-2316, NIFI-2318: Ensure that we do not save the flow before
initializing the Run Status of components. Clarify the Node Event messages
----
> After restarting cluster, all nodes sometimes come up with all components
> stopped
> ---------------------------------------------------------------------------------
>
> Key: NIFI-2316
> URL: https://issues.apache.org/jira/browse/NIFI-2316
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
> Affects Versions: 1.0.0
> Reporter: Mark Payne
> Assignee: Mark Payne
> Priority: Blocker
> Fix For: 1.0.0
>
>
> When I restart an entire cluster, I see sometimes that all processors, etc.
> are stopped. Sometimes this can also result in some nodes not being able to
> join the cluster if they have a root group port, as the run status is not the
> same across the cluster, so the new node cannot inherit the flow.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
