hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Naganarasimha G R (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (YARN-3946) Allow fetching exact reason as to why a submitted app is in ACCEPTED state in CS
Date Fri, 04 Dec 2015 18:30:11 GMT

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

Naganarasimha G R updated YARN-3946:
------------------------------------
    Attachment: YARN-3946.v1.006.patch

Hi [~wangda],
Attaching a patch with corrections for test case and removing duplicate method in SchedulerApplicationAttempt

> Allow fetching exact reason as to why a submitted app is in ACCEPTED state in CS
> --------------------------------------------------------------------------------
>
>                 Key: YARN-3946
>                 URL: https://issues.apache.org/jira/browse/YARN-3946
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: capacity scheduler, resourcemanager
>    Affects Versions: 2.6.0
>            Reporter: Sumit Nigam
>            Assignee: Naganarasimha G R
>         Attachments: 3946WebImages.zip, YARN-3946.v1.001.patch, YARN-3946.v1.002.patch,
YARN-3946.v1.003.Images.zip, YARN-3946.v1.003.patch, YARN-3946.v1.004.patch, YARN-3946.v1.005.patch,
YARN-3946.v1.006.patch
>
>
> Currently there is no direct way to get the exact reason as to why a submitted app is
still in ACCEPTED state. It should be possible to know through RM REST API as to what aspect
is not being met - say, queue limits being reached, or core/ memory requirement not being
met, or AM limit being reached, etc.



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

Mime
View raw message