Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: yarn-issues@hadoop.apache.org
Date: Wed, 9 Dec 2015 02:48:10 +0000 (UTC)
From: "Xianyin Xin (JIRA)" <jira@apache.org>
To: yarn-issues@hadoop.apache.org
Message-ID: <JIRA.12918080.1449166503000.308246.1449629290969@Atlassian.JIRA>
In-Reply-To: <JIRA.12918080.1449166503000@Atlassian.JIRA>
References: <JIRA.12918080.1449166503000@Atlassian.JIRA>
 <JIRA.12918080.1449166503425@arcas>
Subject: [jira] [Commented] (YARN-4415) Scheduler Web Ui shows max capacity
 for the queue is 100% but when we submit application doesnt get assigned
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Xianyin Xin commented on YARN-4415:
-----------------------------------

+1 for the general idea from [~Naganarasimha]. I think there exists many improper in the code, especially when dealing with label "*", like {{setupQueueConfigs()}} in {{AbstractCSQueue}} and, the {{PartitionQueueCapacitiesInfo}} and {{QueueCapacitiesInfo}} when return the actually capacities. I suggest you just upload a preview patch so that the problem can exposed in another way, sounds feasible?

> 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)