hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-6042) Fairscheduler: Dump scheduler state in log
Date Tue, 14 Feb 2017 19:35:42 GMT

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

ASF GitHub Bot commented on YARN-6042:
--------------------------------------

GitHub user flyrain opened a pull request:

    https://github.com/apache/hadoop/pull/193

    YARN-6042. Fairscheduler: Dump scheduler state in log.

    

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/flyrain/hadoop yarn-6042

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/hadoop/pull/193.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #193
    
----
commit de6c969973d5b50aa2b461be1560b1e9b80cc9dc
Author: Yufei Gu <yufei.gu@cloudera.com>
Date:   2017-01-13T01:35:17Z

    YARN-6042. Fairscheduler: Dump scheduler state in log.

----


> 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: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org


Mime
View raw message