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

Posted to github@beam.apache.org by GitBox <gi...@apache.org> on 2022/06/04 15:25:59 UTC

[GitHub] [beam] damccorm opened a new issue, #20078: MemoryMonitor thrashing detection is too aggressive for batch workers

damccorm opened a new issue, #20078:
URL: https://github.com/apache/beam/issues/20078

   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.
   
   Imported from Jira [BEAM-9049](https://issues.apache.org/jira/browse/BEAM-9049). Original Jira may contain additional context.
   Reported by: bhulette.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: github-unsubscribe@beam.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org