[
https://issues.apache.org/jira/browse/NIFI-619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15370632#comment-15370632
]
ASF GitHub Bot commented on NIFI-619:
-------------------------------------
Github user JPercivall commented on the issue:
https://github.com/apache/nifi/pull/575
Hey @ijokarumawak,
I'm gonna be reviewing this today but did you check out the Travis build?
It is failing on a MonitorActivity Test:
Tests run: 7, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 9.555 sec
<<< FAILURE! - in org.apache.nifi.processors.standard.TestMonitorActivity
testClusterMonitorActivityRestoredBySelf(org.apache.nifi.processors.standard.TestMonitorActivity)
Time elapsed: 0.015 sec <<< FAILURE!
java.lang.AssertionError: Latest timestamp should be persisted
at org.junit.Assert.fail(Assert.java:88)
at org.junit.Assert.assertTrue(Assert.java:41)
at org.junit.Assert.assertNotNull(Assert.java:712)
at
org.apache.nifi.processors.standard.TestMonitorActivity.testClusterMonitorActivityRestoredBySelf(TestMonitorActivity.java:323)
> 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)
