[
https://issues.apache.org/jira/browse/YARN-3946?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14634972#comment-14634972
]
Naganarasimha G R commented on YARN-3946:
-----------------------------------------
Hi [~sumit.nigam] & [~varun_saxena], Yes there are enough information in the
UI but the user needs to know all the intricacies of the scheduler to
understand it, in most of the cases user might not have the understanding to
relate the content present in WEB UI, so simple diagnostic message in WEB UI's
applications page/CLI/REST will be faster to analyze it and further contact
with the admin. Thoughts ?
> 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)
