[
https://issues.apache.org/jira/browse/NIFI-2431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Payne updated NIFI-2431:
-----------------------------
Issue Type: Sub-task (was: Bug)
Parent: NIFI-2419
> 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)
