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 "XiandongQI (JIRA)" <ji...@apache.org> on 2018/07/04 12:34:00 UTC
[jira] [Comment Edited] (YARN-8379) Improve balancing resources in
already satisfied queues by using Capacity Scheduler preemption
[ https://issues.apache.org/jira/browse/YARN-8379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16532677#comment-16532677 ]
XiandongQI edited comment on YARN-8379 at 7/4/18 12:33 PM:
-----------------------------------------------------------
if a container with a label is released, the current "PriorityUtilizationQueueOrderingPolicy.java" will give it to the user(leafquque) who has the access to this partition and has a lower absolute used capacity if all users have the same priority.
That is to say, the policy will prepare an assignmentIterator for each partition.
was (Author: xiandongqi):
if a container with a label is released, the current "PriorityUtilizationQueueOrderingPolicy.java" will give it to the user(leafquque) who has the access to this partition and has a lower absolute used capacity if all users have the same priority.
> Improve balancing resources in already satisfied queues by using Capacity Scheduler preemption
> ----------------------------------------------------------------------------------------------
>
> Key: YARN-8379
> URL: https://issues.apache.org/jira/browse/YARN-8379
> Project: Hadoop YARN
> Issue Type: Bug
> Reporter: Wangda Tan
> Assignee: Zian Chen
> Priority: Major
> Fix For: 3.2.0, 3.1.1
>
> Attachments: YARN-8379.001.patch, YARN-8379.002.patch, YARN-8379.003.patch, YARN-8379.004.patch, YARN-8379.005.patch, YARN-8379.006.patch, ericpayne.confs.tgz
>
>
> Existing capacity scheduler only supports preemption for an underutilized queue to reach its guaranteed resource. In addition to that, there’s an requirement to get better balance between queues when all of them reach guaranteed resource but with different fairness resource.
> An example is, 3 queues with capacity, queue_a = 30%, queue_b = 30%, queue_c = 40%. At time T. queue_a is using 30%, queue_b is using 70%. Existing scheduler preemption won't happen. But this is unfair to queue_a since queue_a has the same guaranteed resources.
> Before YARN-5864, capacity scheduler do additional preemption to balance queues. We changed the logic since it could preempt too many containers between queues when all queues are satisfied.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org