[
https://issues.apache.org/jira/browse/NIFI-4075?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16052014#comment-16052014
]
Mark Payne commented on NIFI-4075:
----------------------------------
[~JPercivall] very happy to see you jumping on this! I don't think this is
needed for Reporting Tasks, because on startup, if a Reporting Task is
configured to run, it immediately starts running. Components in your flow may
not actually start running immediately because they need to wait for the
FlowFile Repository to be initialized (which happens after joining the cluster
for a clustered instance). So Reporting Tasks should already have the correct
Scheduled State when the code enters the StandardFlowSerializer.
Thanks
-Mark
> Inconsistent State for RPGs
> ---------------------------
>
> Key: NIFI-4075
> URL: https://issues.apache.org/jira/browse/NIFI-4075
> Project: Apache NiFi
> Issue Type: Bug
> Affects Versions: 1.3.0
> Reporter: Bryan Bende
> Priority: Blocker
> Fix For: 1.4.0
>
>
> It was reported on the mailing list that RPGs were shown as
> enabled/transmitting in the UI, but were not actually running.
> After investigating, it appears this could be related to NIFI-3900 that was
> addressed in 1.3.0.
> That fix introduced a ScheduledStateLookUp which was used for determining the
> state of processors and ports, for example:
> https://github.com/apache/nifi/blob/master/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-framework-core/src/main/java/org/apache/nifi/controller/serialization/StandardFlowSerializer.java#L354
> But it appears to not be used for RemoteGroupPorts:
> https://github.com/apache/nifi/blob/master/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-framework-core/src/main/java/org/apache/nifi/controller/serialization/StandardFlowSerializer.java#L314
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
