[
https://issues.apache.org/jira/browse/NIFI-4310?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Payne updated NIFI-4310:
-----------------------------
Resolution: Fixed
Fix Version/s: 1.4.0
Status: Resolved (was: Patch Available)
> Certain flow configurations are improperly identified as empty during flow
> election
> -----------------------------------------------------------------------------------
>
> Key: NIFI-4310
> URL: https://issues.apache.org/jira/browse/NIFI-4310
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
> Affects Versions: 1.3.0
> Reporter: Yolanda M. Davis
> Assignee: Yolanda M. Davis
> Fix For: 1.4.0
>
>
> 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.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
