Details
-
Bug
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
1.3.0
-
None
Description
While testing a cluster containing nodes with two different flows on initial startup, I discovered that one flow, with an empty root processor group but containing reporting tasks, would lose a flow election against flows that also had empty root processor groups yet with no reporting tasks or controller tasks. This caused an issue downstream during startup where it attempted to replace the non-empty flow with an empty flow on certain nodes, which led to UninheritableFlowExceptions. Further investigation revealed that during election there is a check to determine if the flow is empty however the check does not account for the existence of a reporting task or controller services. This should be repaired to ensure that flows are properly identified as non-empty for election.
Attachments
Issue Links
- links to
