hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ray Chiang (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-6042) Dump scheduler and queue state information into FairScheduler DEBUG log
Date Fri, 24 Feb 2017 00:35:44 GMT

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

Ray Chiang commented on YARN-6042:

Very minor nit:

The result of this part of code:

    rootMetrics.getAvailableMB(), rootMetrics.getAvailableVirtualCores()) +

There is no separation between the scheduler and the queue states.   From my sample output,
the part in red looks a little odd:

2017-02-23 14:53:29,644 DEBUG fair.FairScheduler: FairScheduler state: Cluster Capacity: <memory:0,
vCores:0>  Allocations: <memory:0, vCores:0>  Availability: <memory:0, vCores:0{color:red}>{{color}Name:
root, Weight: <memory weight=1.0, cpu weight=1.0>, Policy: fair, FairShare: <memory:0,
vCores:0>, SteadyFairShare: <memory:0, vCores:0>,

I'd suggest adding two spaces and possibly a label like the rest of the scheduler state?

> Dump scheduler and queue state information into FairScheduler DEBUG 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, YARN-6042.003.patch, YARN-6042.004.patch,
YARN-6042.005.patch, YARN-6042.006.patch, YARN-6042.007.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

To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org

View raw message