[
https://issues.apache.org/jira/browse/NIFI-4310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16141676#comment-16141676
]
ASF subversion and git services commented on NIFI-4310:
-------------------------------------------------------
Commit 0eda71a9a642432accc536206516df0f114b176a in nifi's branch
refs/heads/master from [~YolandaMDavis]
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=0eda71a ]
NIFI-4310 - added changes to support detection of reporting tasks and
controller services during isEmpty flow check. Added testing scenarios. This
closes #2107.
> 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
>
> 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)
