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

Wilfred Spiegelenburg commented on YARN-10124:
----------------------------------------------

Based on what I read here is that you expect a stopped queue to not have a 
capacity and thus return 0 when calculating the correct distributing. If that 
is the use case then why can't we implement that. In other words: why not turn 
this around, only return or take into account the capacity of a queue when it 
is not in a stopped state? So you return 0 for all stopped queues. You do not 
have to go further than that.

No need to (re)calculate below the parent that is stopped 0 (as that is all 
ignored) and turning the queue back on will trigger the existing settings to be 
applied again without further changes.

> Remove restriction of ParentQueue capacity zero when childCapacities > 0
> ------------------------------------------------------------------------
>
>                 Key: YARN-10124
>                 URL: https://issues.apache.org/jira/browse/YARN-10124
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: capacity scheduler
>    Affects Versions: 3.3.0
>            Reporter: Prabhu Joseph
>            Assignee: Prabhu Joseph
>            Priority: Major
>         Attachments: YARN-10124-001.patch
>
>
> ParentQueue capacity cannot be set to 0 when child capacities > 0. To disable 
> a parent queue temporarily, user can only STOP the queue but the capacity of 
> the queue cannot be used for other queues. Allowing 0 capacity for parent 
> queue will allow user to use the capacity for other queues and also to retain 
> the child queue capacity values. (else user has to set all child queue 
> capacities to 0)



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org

Reply via email to