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

Naganarasimha G R commented on YARN-4415:
-----------------------------------------

As per offline discussion with [~wangda] he had mentioned that it was done with 
intent that the default max capacity of a  partition is set to zero to avoid 
configuring the queue.
IMHO i feel its much easier if we assume max capacity is 100% and calculate abs 
max based on its parent queue's max cap for following reasons
# It will have the same behavior as that of default partition hence less 
confusion
# May be my understanding is wrong but i feel its easier to add new partitions 
without touching the CS.xml as we can set the accessible nodelabels to * and 
assume 100% as the max capacity and 0% as guranteed capacity.

And also we need to update the documentation with the default values


> Scheduler Web Ui shows max capacity for the queue is 100% but when we submit 
> application doesnt get assigned
> ------------------------------------------------------------------------------------------------------------
>
>                 Key: YARN-4415
>                 URL: https://issues.apache.org/jira/browse/YARN-4415
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: capacity scheduler, resourcemanager
>    Affects Versions: 2.7.2
>            Reporter: Naganarasimha G R
>            Assignee: Naganarasimha G R
>         Attachments: App info with diagnostics info.png, screenshot-1.png
>
>
> Steps to reproduce the issue :
> Scenario 1:
> # Configure a queue(default) with accessible node labels as *
> # create a exclusive partition *xxx* and map a NM to it
> # ensure no capacities are configured for default for label xxx
> # start an RM app with queue as default and label as xxx
> # application is stuck but scheduler ui shows 100% as max capacity for that 
> queue
> Scenario 2:
> # create a nonexclusive partition *sharedPartition* and map a NM to it
> # ensure no capacities are configured for default queue
> # start an RM app with queue as *default* and label as *sharedPartition*
> # application is stuck but scheduler ui shows 100% as max capacity for that 
> queue for *sharedPartition*
> For both issues cause is the same default max capacity and abs max capacity 
> is set to Zero %



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to