[
https://issues.apache.org/jira/browse/NIFI-1966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15453048#comment-15453048
]
ASF GitHub Bot commented on NIFI-1966:
--------------------------------------
GitHub user markap14 opened a pull request:
https://github.com/apache/nifi/pull/977
NIFI-1966: When cluster is started up, do not assume that Cluster Coo…
…rdinator has the golden copy of the flow but instead wait for some period
of time or until the required number of nodes have connected, and then choose
which flow is correct
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/markap14/nifi NIFI-1966
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/nifi/pull/977.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 #977
----
commit 6497d0adac2369b608e809660311b34d680fc595
Author: Mark Payne <[email protected]>
Date: 2016-08-30T20:59:50Z
NIFI-1966: When cluster is started up, do not assume that Cluster
Coordinator has the golden copy of the flow but instead wait for some period of
time or until the required number of nodes have connected, and then choose
which flow is correct
----
> Address Issue of Nodes Disagreeing About Flow Contents on Startup
> -----------------------------------------------------------------
>
> Key: NIFI-1966
> URL: https://issues.apache.org/jira/browse/NIFI-1966
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
> Reporter: Matt Gilman
> Assignee: Mark Payne
> Priority: Blocker
> Fix For: 1.1.0
>
>
> During startup a coordinator is selected at random to act as the manager of
> data flow and distributing it to other nodes. This works fine unless that
> selected coordinator happens to have a uninheritable data flow. When this
> occurs, the other nodes either are
> - Able to connect to Coordinator and then unable to join due to an
> uninheritable flow exception due to being presented with a bad data flow. In
> this case, the node shut down.
> - Unable to connect to the Coordinator due to lack of quorem and never
> present with the bad data flow. In this case, the node ran its local flow.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
