[ 
https://issues.apache.org/jira/browse/YARN-7520?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16274291#comment-16274291
 ] 

Sunil G edited comment on YARN-7520 at 12/1/17 11:42 AM:
---------------------------------------------------------

In {{PriorityUtilizationQueueOrderingPolicy#compare}}, we have an else 
condition as follows.
{code}
else {
       return 0;
}
{code}
This will happen when q1AbsCapacity  = 0 && q2AbsCapacity = 0. I think when 
capacity is 0, but max capacity is configured, some of this queue might be 
using some capacity. so we have to compare with used capacity here, correct?


was (Author: sunilg):
In {{PriorityUtilizationQueueOrderingPolicy#compare}}, we have an else 
condition as follows.
{code}
else {
       return 0;
}
{code}
This will happen when q1AbsCapacity  = 0 && q2AbsCapacity = 0. I think when 
capacity is 0, but max capacity is configured, some of this queue might  using 
some capacity. so we have to compare with used capacity here

> Queue Ordering policy changes for ordering auto created leaf queues within 
> Managed parent Queues
> ------------------------------------------------------------------------------------------------
>
>                 Key: YARN-7520
>                 URL: https://issues.apache.org/jira/browse/YARN-7520
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: capacity scheduler
>            Reporter: Suma Shivaprasad
>            Assignee: Suma Shivaprasad
>         Attachments: YARN-7520.1.patch, YARN-7520.2.patch
>
>
> Queue Ordering policy currently uses priority, utilization and absolute 
> capacity for pre-configured parent queues to order leaf queues while 
> assigning containers. It needs modifications for auto created leaf queues 
> since they can have zero capacity



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to