[
https://issues.apache.org/jira/browse/YARN-6042?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15866446#comment-15866446
]
Yufei Gu commented on YARN-6042:
--------------------------------
Thanks [~wilfreds]'s review.
1. Pass rootQueue to the method doesn't change much since rootQueue is a member
of QueueManager
2. Fixed in new patch.
3. Some changes in trunk removed {{getLastTimeAtFairShareThreshold()}}
4. {{ControlledClock}} is used in test case, so the clock won't run unless we
manually {{tick}} it.
5. As our offline discussion, I add more log into several steps of assigning
containers to resource requests.
> Fairscheduler: Dump scheduler state in log
> ------------------------------------------
>
> Key: YARN-6042
> URL: https://issues.apache.org/jira/browse/YARN-6042
> Project: Hadoop YARN
> Issue Type: Improvement
> Components: fairscheduler
> Reporter: Yufei Gu
> Assignee: Yufei Gu
> Attachments: YARN-6042.001.patch, YARN-6042.002.patch
>
>
> To improve the debugging of scheduler issues it would be a big improvement to
> be able to dump the scheduler state into a log on request.
> The Dump the scheduler state at a point in time would allow debugging of a
> scheduler that is not hung (deadlocked) but also not assigning containers.
> Currently we do not have a proper overview of what state the scheduler and
> the queues are in and we have to make assumptions or guess
> The scheduler and queue state needed would include (not exhaustive):
> - instantaneous and steady fair share (app / queue)
> - AM share and resources
> - weight
> - app demand
> - application run state (runnable/non runnable)
> - last time at fair/min share
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
