[ https://issues.apache.org/jira/browse/BEAM-690?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17132144#comment-17132144 ]
Beam JIRA Bot commented on BEAM-690: ------------------------------------ This issue is P2 but has been unassigned without any comment for 60 days so it has been labeled "stale-P2". If this issue is still affecting you, we care! Please comment and remove the label. Otherwise, in 14 days the issue will be moved to P3. Please see https://beam.apache.org/contribute/jira-priorities/ for a detailed explanation of what these priorities mean. > 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: P2 > Labels: stale-P2 > 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.3.4#803005)