[
https://issues.apache.org/jira/browse/NIFI-2431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15399323#comment-15399323
]
ASF GitHub Bot commented on NIFI-2431:
--------------------------------------
GitHub user markap14 opened a pull request:
https://github.com/apache/nifi/pull/742
NIFI-2431: Before registering for the Cluster Coordinator role, check…
… if another node already has this role. If so, do not register for this
role until after the node has joined the cluster and inherited the flow.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/markap14/nifi NIFI-2431
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/nifi/pull/742.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 #742
----
commit d0333bb499daafbeb3580be5992949a93414e6c2
Author: Mark Payne <[email protected]>
Date: 2016-07-29T13:14:17Z
NIFI-2431: Before registering for the Cluster Coordinator role, check if
another node already has this role. If so, do not register for this role until
after the node has joined the cluster and inherited the flow.
----
> When a new node joins cluster, it can be elected Cluster Coordinator even if
> its flow is different than cluster's
> -----------------------------------------------------------------------------------------------------------------
>
> Key: NIFI-2431
> URL: https://issues.apache.org/jira/browse/NIFI-2431
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
> Affects Versions: 1.0.0
> Reporter: Mark Payne
> Assignee: Mark Payne
> Priority: Blocker
> Fix For: 1.0.0
>
>
> I have a 3 node cluster. I started 2 out of the three. I then removed the
> flow from the third node and started the third node, expecting it to inherit
> the flow from the cluster. However, when it started up, it was elected
> Cluster Coordinator before inheriting the flow. As a result, it determined
> that its flow (the empty flow) was correct. The other two nodes were then
> dropped from the cluster for having incompatible flows.
> The desired behavior is that the third node will not become Cluster
> Coordinator if a cluster already exists with an agreed-upon flow.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
