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 "Ray Chiang (JIRA)" <ji...@apache.org> on 2016/08/25 22:58:20 UTC

[jira] [Updated] (YARN-5563) Add log messages for jobs in ACCEPTED state but not runnable.

     [ https://issues.apache.org/jira/browse/YARN-5563?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ray Chiang updated YARN-5563:
-----------------------------
    Issue Type: Sub-task  (was: Improvement)
        Parent: YARN-5397

> Add log messages for jobs in ACCEPTED state but not runnable.
> -------------------------------------------------------------
>
>                 Key: YARN-5563
>                 URL: https://issues.apache.org/jira/browse/YARN-5563
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: fairscheduler
>            Reporter: Yufei Gu
>            Assignee: Yufei Gu
>
> Leaf queues maintain a list of runnable and non-runnable apps. FairScheduler marks an app non-runnable for different reasons: exceeding (1) queue max apps, (2) user max apps, (3) queue maxResources, (4) maxAMShare. It would be nice to log the reason an app isn't runnable. The first three are easy to infer, but the last one (maxAMShare) is particularly hard. It would be nice to log at least that.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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