[NIFI-9729] If a component is stopped while a node is disconnected from cluster, node may not be updated when rejoining

• Type: Bug
• Status: Resolved
• Priority: Blocker
• Resolution: Fixed
• Fix Version/s: 1.16.0
• Component/s: Core Framework
• Assignee: Mark Payne
• Reporter: Mark Payne
• Created: 25/Feb/22 16:42
• Updated: 25/Feb/22 19:30
• Resolved: 25/Feb/22 19:30

Description

This issue does not affect any already-released version of NiFi. It affects only 1.16.0-SNAPSHOT.

To replicate:

• Have a running NiFi cluster
• Start components on the canvas
• Disconnect a node
• Stop one of the components
• Reconnect the node
• Once the node is reconnected, the component should be stopped (or stopping) but currently will still be running.

The opposite does not appear to be a concern. I.e., if a component was stopped, and changed to running while the node is disconnected, the node will properly update the component state and start running the component upon rejoining the cluster.

Issue Links

• links to: GitHub Pull Request #5806