hadoop-yarn-issues mailing list archives

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

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

Wangda Tan commented on YARN-3946:
----------------------------------

Looks good, +1. Thanks [~Naganarasimha], will wait a few days to see if anybody wants to take
a look at the patch.

> 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, YARN-3946.v1.007.patch, YARN-3946.v1.008.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