[
https://issues.apache.org/jira/browse/NIFI-619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15372853#comment-15372853
]
ASF GitHub Bot commented on NIFI-619:
-------------------------------------
Github user ijokarumawak commented on the issue:
https://github.com/apache/nifi/pull/575
@JPercivall Thanks for reviewing this.
For the 1st comment:
I didn't notice that it's failing Travis test... I'll check what caused the
error. Thanks for pointing that.
For the 2nd and last comment:
> When running clustered and monitoring on the cluster, it needs to take
into account generating the inactive flowfiles 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.
I wrote onTrigger like that intentionally, because I thought there're
use-cases in which user would like to do something on each node when NiFi went
inactive or recovered activity. If one would like to get notification flow-file
only on a single node in the cluster, then they can use `On primary node`
scheduling strategy. Excuse me if I misunderstood your comments, but does this
address your concern?
> 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)
