[NIFI-2431] When a new node joins cluster, it can be elected Cluster Coordinator even if its flow is different than cluster's

• Type: Sub-task
• Status: Resolved
• Priority: Blocker
• Resolution: Fixed
• Affects Version/s: 1.0.0
• Fix Version/s: 1.0.0, 1.0.0-Beta
• Component/s: Core Framework
• Assignee: Joe Witt
• Reporter: Mark Payne
• Created: 29/Jul/16 13:13
• Updated: 04/Aug/16 21:23
• Resolved: 29/Jul/16 15:24

Description

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.

Issue Links

• links to: GitHub Pull Request #742