[
https://issues.apache.org/jira/browse/NIFI-619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15370966#comment-15370966
]
ASF GitHub Bot commented on NIFI-619:
-------------------------------------
Github user JPercivall commented on the issue:
https://github.com/apache/nifi/pull/575
When running clustered and monitoring on the cluster, it needs to take into
account generating the inactive flowfiles[1] in a cluster friendly way as well.
Currently each Node will generate a flowfile when the inactivity time hits.
Probably need to track in clustered state whether or not a marker has been sent.
[1]
https://github.com/apache/nifi/blob/3726e34eb6cb5c568ee14fa0262faf1968435dd8/nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors/src/main/java/org/apache/nifi/processors/standard/MonitorActivity.java#L233-L233
> update MonitorActivity processor to be cluster friendly
> -------------------------------------------------------
>
> Key: NIFI-619
> URL: https://issues.apache.org/jira/browse/NIFI-619
> Project: Apache NiFi
> Issue Type: Improvement
> Reporter: Brandon DeVries
> Assignee: Koji Kawamura
> Priority: Minor
> Fix For: 1.0.0
>
>
> This processor should be able to be used to monitor activity across the
> cluster. In its current state, alerting is based on activity of a single
> node, not the entire cluster.
> For example, in a 2 node cluster, if system A is getting data from a given
> flow and system B is not, system B will alert for lack of activity even
> though the flow is functioning "normally".
> The ideal behavior would be fore an alert to be generated only if both
> systems did not see data in the specified time.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
