[
https://issues.apache.org/jira/browse/NIFI-1966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15474060#comment-15474060
]
ASF subversion and git services commented on NIFI-1966:
-------------------------------------------------------
Commit bc7c42efa53b363741a974a7fcf25e04f9208086 in nifi's branch
refs/heads/master from [~markap14]
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=bc7c42e ]
NIFI-1966: Recreated issue that is outlined in JIRA (the reason for re-opening
the ticket) that results in 'java.util.NoSuchElementException: No value
present' in unit test - Resolved issue where two flows that are both empty but
have different fingerprints (due to root group id being different) causes vote
election to fail
This closes #995.
Signed-off-by: Bryan Bende <[email protected]>
> 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)
