Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: yarn-issues@hadoop.apache.org
Date: Wed, 2 Sep 2015 02:47:46 +0000 (UTC)
From: "Rohith Sharma K S (JIRA)" <jira@apache.org>
To: yarn-issues@hadoop.apache.org
Message-ID: <JIRA.12861195.1441158088000.230533.1441162066277@Atlassian.JIRA>
In-Reply-To: <JIRA.12861195.1441158088000@Atlassian.JIRA>
References: <JIRA.12861195.1441158088000@Atlassian.JIRA>
 <JIRA.12861195.1441158088426@arcas>
Subject: [jira] [Commented] (YARN-4104) dryrun of schedule for diagnostic
 and tenant's complain
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Rohith Sharma K S commented on YARN-4104:
-----------------------------------------

Thanks [~zhiguohong] for brining up the customer pain point. In YARN-4091 trying to make debuggabiliy easy. Making subtask of the YARN-4091.

> dryrun of schedule for diagnostic and tenant's complain
> -------------------------------------------------------
>
>                 Key: YARN-4104
>                 URL: https://issues.apache.org/jira/browse/YARN-4104
>             Project: Hadoop YARN
>          Issue Type: Improvement
>          Components: scheduler
>            Reporter: Hong Zhiguo
>            Assignee: Hong Zhiguo
>            Priority: Minor
>
> We have more than 1 thousand queues and several hundreds of tenants in a busy cluster. We get a lot of complains/questions from owner/operator of queues about "Why my queue/app can't get resource for a long while? "
> It's really hard to answer such questions.
> So we added a diagnostic REST endpoint "/ws/v1/cluster/schedule/dryrun/{parentQueueName}" which returns the sorted list of it's children according to it's SchedulingPolicy.getComparator().  All scheduling parameters of the children are also displayed, such as minShare, usage, demand, weight, priority etc.
> Usually we just call "/ws/v1/cluster/schedule/dryrun/root", and the result self-explains to the questions.
> I feel it's really useful for multi-tenant clusters, and hope it could be merged into the mainline.


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