[
https://issues.apache.org/jira/browse/YARN-6042?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yufei Gu updated YARN-6042:
---------------------------
Description:
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
was:
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
> 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
>
> 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.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
