[
https://issues.apache.org/jira/browse/NIFI-1966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15472360#comment-15472360
]
ASF GitHub Bot commented on NIFI-1966:
--------------------------------------
GitHub user markap14 opened a pull request:
https://github.com/apache/nifi/pull/995
NIFI-1966: 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
First Commit is a unit test that replicates the issue. This will fail
without the second commit being applied. After applying the second commit, the
tests should all pass.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/markap14/nifi NIFI-1966-Part2
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/nifi/pull/995.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 #995
----
commit dd2b47edff1a2c47afcc85d54a1024e5814e63a0
Author: Mark Payne <[email protected]>
Date: 2016-09-08T01:07:01Z
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
commit 9db7d47826a76f1a5ad0acd9c1c476c0892fbd4c
Author: Mark Payne <[email protected]>
Date: 2016-09-08T01:15:41Z
NIFI-1966: 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
----
> 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)
