[NIFI-3900] Cluster - Inconsistent schedule state across the cluster

• Type: Bug
• Status: Resolved
• Priority: Critical
• Resolution: Fixed
• Fix Version/s: 1.3.0
• Component/s: Core Framework
• Assignee: Mark Payne
• Reporter: Matt Gilman
• Created: 15/May/17 19:33
• Updated: 23/May/17 17:16
• Resolved: 16/May/17 20:05

Description

When nodes join a cluster there appears to be a timing issue that causes inconsistency with the scheduled state of components across the cluster. Due to delayed initialization, component's schedule state may be incorrect when a proposed flow is sent to a node.

It appears that a node will get an inconsistent scheduled states when it's not able to connect to the cluster initially and receives a try-again-later response from the coordinator.

Issue Links

• is duplicated by: NIFI-3922 Inconsistency in Resume, Stop, Start of Processors/Controller Services
• links to: GitHub Pull Request #1804