[
https://issues.apache.org/jira/browse/NIFI-1966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15470763#comment-15470763
]
Matt Gilman commented on NIFI-1966:
-----------------------------------
Adding migration label as we need to document the new properties for voting on
the flow.
> 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
> Labels: migration
> 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)
