[
https://issues.apache.org/jira/browse/BEAM-690?focusedWorklogId=141231&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-141231
]
ASF GitHub Bot logged work on BEAM-690:
---------------------------------------
Author: ASF GitHub Bot
Created on: 05/Sep/18 13:11
Start Date: 05/Sep/18 13:11
Worklog Time Spent: 10m
Work Description: iemejia commented on issue #6303: [BEAM-690] Backoff in
the DirectRunner if no work is available
URL: https://github.com/apache/beam/pull/6303#issuecomment-418724981
This LGTM, but I am far from a direct runner expert, so asking for a double
check, for suggestions that I can be missing.
R: @ryanskraba @lukecwik
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 141231)
Time Spent: 20m (was: 10m)
> Backoff in the DirectRunner Monitor if no work is Available
> -----------------------------------------------------------
>
> Key: BEAM-690
> URL: https://issues.apache.org/jira/browse/BEAM-690
> Project: Beam
> Issue Type: Bug
> Components: runner-direct
> Reporter: Thomas Groh
> Priority: Major
> Time Spent: 20m
> Remaining Estimate: 0h
>
> When a Pipeline has no elements available to process, the Monitor Runnable
> will be repeatedly scheduled. Given that there is no work to be done, this
> will loop over the steps in the transform looking for timers, and prompt the
> sources to perform additional work, even though there is no work to be done.
> This consumes the entirety of a single core.
> Add a bounded backoff to rescheduling the monitor runnable if no work has
> been done since it last ran. This will reduce resource consumption on
> low-throughput Pipelines.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
