You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-issues@hadoop.apache.org by "Eric Payne (Jira)" <ji...@apache.org> on 2021/02/25 19:16:00 UTC
[jira] [Comment Edited] (YARN-10613) Config to allow Intra- and
Inter-queue preemption to enable/disable conservativeDRF
[ https://issues.apache.org/jira/browse/YARN-10613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17291154#comment-17291154 ]
Eric Payne edited comment on YARN-10613 at 2/25/21, 7:15 PM:
-------------------------------------------------------------
Thanks [~Jim_Brennan]. I have uploaded the branch-3.2 patch.
It backports cleanly and compiles and preemtion tests pass.
was (Author: eepayne):
Thanks [~Jim_Brennan]. I have uploaded the branch-3.2 patch.
> Config to allow Intra- and Inter-queue preemption to enable/disable conservativeDRF
> ------------------------------------------------------------------------------------
>
> Key: YARN-10613
> URL: https://issues.apache.org/jira/browse/YARN-10613
> Project: Hadoop YARN
> Issue Type: Improvement
> Components: capacity scheduler, scheduler preemption
> Affects Versions: 3.3.0, 3.2.2, 3.1.4, 2.10.1
> Reporter: Eric Payne
> Assignee: Eric Payne
> Priority: Minor
> Attachments: YARN-10613.branch-2.10.002.patch, YARN-10613.branch-3.2.002.patch, YARN-10613.trunk.001.patch, YARN-10613.trunk.002.patch
>
>
> YARN-8292 added code that prevents CS intra-queue preemption from preempting containers from an app unless all of the major resources used by the app are greater than the user limit for that user.
> Ex:
> | Used | User Limit |
> | <58GB, 58> | <30GB, 300> |
> In this example, only used memory is above the user limit, not used vcores. So, intra-queue preemption will not occur.
> YARN-8292 added the {{conservativeDRF}} flag to {{CapacitySchedulerPreemptionUtils#tryPreemptContainerAndDeductResToObtain}}. If {{conservativeDRF}} is false, containers will be preempted from apps in the example state. If true, containers will not be preempted.
> This flag is hard-coded to false for Inter-queue (cross-queue) preemption and true for intra-queue (in-queue) preemption.
> I propose that in some cases, we want intra-queue preemption to be more aggressive and preempt in the example case. To accommodate that, I propose the addition of a config property.
> Also, we may want inter-queue (cross-queue) preemption to be more conservative, so I propose also making that a configuration property:
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org