[jira] [Updated] (BEAM-690) Backoff in the DirectRunner Monitor if no work is Available

["Kenneth Knowles (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/BEAM-690?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kenneth Knowles updated BEAM-690:
---------------------------------

This Jira ticket has a pull request attached to it, but is still open. Did the pull request resolve the issue? If so, could you please mark it resolved? This will help the project have a clear view of its open issues.

> 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: P3
>          Time Spent: 50m
>  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
(v8.20.1#820001)