[
https://issues.apache.org/jira/browse/NIFI-846?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bryan Bende updated NIFI-846:
-----------------------------
Attachment: NIFI-846.patch
Patch makes the recommended change to set lastSuccessTransfer in an @OnSchedule
method, and updates unit tests accordingly.
> 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
> Assignee: Bryan Bende
> Priority: Minor
> Labels: beginner, newbie
> Fix For: 0.3.0
>
> Attachments: NIFI-846.patch
>
>
> 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)
