You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@nifi.apache.org by "Brandon DeVries (JIRA)" <ji...@apache.org> on 2015/08/13 14:33:45 UTC
[jira] [Created] (NIFI-846) MonitorActivity not setting start of
evaluation period correctly
Brandon DeVries created NIFI-846:
------------------------------------
Summary: MonitorActivity not setting start of evaluation period correctly
Key: NIFI-846
URL: https://issues.apache.org/jira/browse/NIFI-846
Project: Apache NiFi
Issue Type: Bug
Affects Versions: 0.2.1
Reporter: Brandon DeVries
Priority: Minor
MonitorActivity uses a "latestSuccessTransfer" variable to determine inactivity. This is set when the processor is first instantiated, and then on successful receipt of a FlowFile. If NiFi takes longer to start up than the configured threshold to start up, MonitorActivity can emit spurious alerts. Additionally, if the processor is stopped and then restarted after a period greater than its threshold, if it doesn't get a FlowFile on its first run of OnTrigger, it can emit a spurious alert as well.
A possible solution would be to add an @OnScheduled method that does:
{code}
latestSuccessTransfer.set(now);
{code}
This will essentially reset the evaluation period whenever the processor is scheduled to run.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)