Details
-
Bug
-
Status: Resolved
-
Critical
-
Resolution: Fixed
-
None
-
None
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.
Attachments
Issue Links
- is duplicated by
-
NIFI-3922 Inconsistency in Resume, Stop, Start of Processors/Controller Services
-
- Resolved
-
- links to