You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@beam.apache.org by "Beam JIRA Bot (Jira)" <ji...@apache.org> on 2020/08/10 17:07:16 UTC

[jira] [Updated] (BEAM-9049) MemoryMonitor thrashing detection is too aggressive for batch workers

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

Beam JIRA Bot updated BEAM-9049:
--------------------------------
    Labels: stale-P2  (was: )

> MemoryMonitor thrashing detection is too aggressive for batch workers
> ---------------------------------------------------------------------
>
>                 Key: BEAM-9049
>                 URL: https://issues.apache.org/jira/browse/BEAM-9049
>             Project: Beam
>          Issue Type: Improvement
>          Components: runner-dataflow
>            Reporter: Brian Hulette
>            Priority: P2
>              Labels: stale-P2
>          Time Spent: 1h 40m
>  Remaining Estimate: 0h
>
> In the streaming dataflow worker we've implemented push-back so that we will reduce parallelism when there is memory pressure. Since we cannot do this on the batch worker, it doesn't make sense for our thrashing detection to be so aggressive. We should increase the thresholds used for thrashing detection when running on Batch workloads.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)