[NIFI-1966] Address Issue of Nodes Disagreeing About Flow Contents on Startup

• Type: Bug
• Status: Resolved
• Priority: Blocker
• Resolution: Fixed
• Fix Version/s: 1.1.0
• Component/s: Core Framework
• Labels: migration
• Assignee: Mark Payne
• Reporter: Matt Gilman
• Created: 03/Jun/16 14:44
• Updated: 10/Oct/16 18:25
• Resolved: 08/Sep/16 14:50

Description

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.

Issue Links

• is related to: NIFI-1991 Zero Master Cluster: Modifying a disconnected node causes other nodes to not be able to join cluster
• relates to: NIFI-2195 Improve sophistication of how nodes detect and handle differences between local and cluster flows
• links to: GitHub Pull Request #977
• links to: GitHub Pull Request #995