You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-issues@hadoop.apache.org by "Weiwei Yang (JIRA)" <ji...@apache.org> on 2018/07/12 03:49:00 UTC
[jira] [Commented] (YARN-4104) dryrun of schedule for diagnostic
and tenant's complain
[ https://issues.apache.org/jira/browse/YARN-4104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16541087#comment-16541087 ]
Weiwei Yang commented on YARN-4104:
-----------------------------------
I like this idea too, but seems this one gets to obsolete :(
> 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: Sub-task
> 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
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org