[
https://issues.apache.org/jira/browse/BEAM-9049?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17174565#comment-17174565
]
Beam JIRA Bot commented on BEAM-9049:
-------------------------------------
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.
> 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)
