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/07/12 13:55:20 UTC
[jira] [Updated] (NIFI-1966) Address Issue of Nodes Disagreeing
About Flow Contents on Startup
[ https://issues.apache.org/jira/browse/NIFI-1966?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mark Payne updated NIFI-1966:
-----------------------------
Fix Version/s: (was: 1.0.0)
1.1.0
> 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)