[
https://issues.apache.org/jira/browse/NIFI-1452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16023392#comment-16023392
]
ASF subversion and git services commented on NIFI-1452:
-------------------------------------------------------
Commit 232380dbfd59de45c4c6623f141d6e7052c367f9 in nifi's branch
refs/heads/master from [~boardm26]
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=232380d ]
NIFI-1452 on timer-driven yield, use the greater of yield duration or run
schedule
This closes #1832.
> Yield Duration can short circuit long Timer Driven Run Schedule
> ---------------------------------------------------------------
>
> Key: NIFI-1452
> URL: https://issues.apache.org/jira/browse/NIFI-1452
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
> Affects Versions: 0.4.1
> Reporter: Michael Moser
> Assignee: Michael Moser
> Priority: Trivial
>
> This may be a rare use case, but I configured a GetFile processor to be Timer
> Driven with a Run Schedule of 30 secs. Its Yield Duration was default 1 sec.
> I expected GetFile onTrigger() to be called every 30 secs, but it was being
> called every 1 sec most of the time.
> GetFile will call context.yield() when it polls a directory and gets an empty
> list in return. It appears that a yield will ignore the Run Schedule. Many
> standard processors call context.yield() when they have no work to do.
> I changed my scheduling strategy to CRON Driven with its run schedule every
> 30 seconds, and the onTrigger() was called every 30 seconds, even after a
> yield. So CRON Driven scheduling is working as expected after a yield.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
