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

Sumit Nigam updated YARN-3946:
------------------------------
    Description: 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.  (was: 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 able 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.)

> Allow fetching exact reason as to why a submitted app is in ACCEPTED state.
> ---------------------------------------------------------------------------
>
>                 Key: YARN-3946
>                 URL: https://issues.apache.org/jira/browse/YARN-3946
>             Project: Hadoop YARN
>          Issue Type: Improvement
>          Components: resourcemanager
>    Affects Versions: 2.6.0
>            Reporter: Sumit Nigam
>
> 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)

Reply via email to