[
https://issues.apache.org/jira/browse/NIFI-2431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15399497#comment-15399497
]
ASF subversion and git services commented on NIFI-2431:
-------------------------------------------------------
Commit bc0b5fe154c8473220c5a119434e79ca279be2c3 in nifi's branch
refs/heads/master from [~markap14]
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=bc0b5fe ]
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: Sub-task
> Components: Core Framework
> Affects Versions: 1.0.0
> Reporter: Mark Payne
> Assignee: Joseph Witt
> 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)
