beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel Halperin (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (BEAM-690) Backoff in the DirectRunner Monitor if no work is Available
Date Thu, 29 Sep 2016 18:17:20 GMT

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

Daniel Halperin updated BEAM-690:
---------------------------------
    Assignee:     (was: Thomas Groh)

> 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
>
> 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
(v6.3.4#6332)

Mime
View raw message