[NIFI-1452] Yield Duration can short circuit long Timer Driven Run Schedule - ASF JIRA

Attach files

Attach Screenshot

Voters

Watch issue

Watchers

Create sub-task

Link

Clone

Update Comment Author

Replace String in Comment

Update Comment Visibility

Delete Comments

XML

Word

Printable

JSON

Details

Type: Bug
Status: Resolved
Priority: Trivial
Resolution: Fixed
Affects Version/s: 0.4.1
Fix Version/s: 1.3.0
Component/s: Core Framework
Labels:
None

Description

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.