[
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.004.patch
Hi [~wangda]
*TestAMAuthorization and TestClientRMTokens* test cases are not related to
this issue and already there are jiras addressing these testcase failures, but
{{TestApplicationLimitsByPartition}} is related to the patch which i have
corrected and also have covered one case when application is not assigned to a
node, diagnostics shows the information of the node and the reason.
> 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
>
>
> 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)
