[
https://issues.apache.org/jira/browse/BEAM-9049?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kenneth Knowles updated BEAM-9049:
----------------------------------
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.
> 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: P3
> Time Spent: 1h 50m
> 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.20.1#820001)
