[
https://issues.apache.org/jira/browse/YARN-4415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15057134#comment-15057134
]
Xianyin Xin commented on YARN-4415:
-----------------------------------
Hi [~leftnoteasy], thanks for you comments.
{quote}
You can see that there're different pros and cons to choose default values of
the two options. Frankly I don't have strong preference for all these choices.
But since we have decided default values since 2.6, I would suggest don't
change the default values.
{quote}
i understand and respect your choice. The pros and cons are just the two sides
of a coin, we must choose one. But i just feel it strange that the
access-labels are "\*" but in fact we can't access it. so in this case "\*"
means nothing except that it is just a symbol, or a abbreviation of all labels.
(what i mean is it has something contradiction with intuition when one sees
"*", i think naga has the same sense). You can claim that the access-labels and
max-capacities are two things and if we want to use it, we must set the two
separately and explicitly. If we finally choose such the way it works, i will
reserve my opinion. At last, thanks again. :)
> 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,
> capacity-scheduler.xml, 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)
