[
https://issues.apache.org/jira/browse/YARN-3946?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14634956#comment-14634956
]
Varun Saxena commented on YARN-3946:
------------------------------------
[~sumit.nigam], thanks for reporting the issue.
There have been changes recently in RM Scheduler Page(primarily for Capacity
Scheduler) in 2.7.0 to enable better debugging of such situations.
It gives an internal view of whats happening in scheduler.
If a submitted app is not moving from ACCEPTED state to RUNNING state because
AM cannot be launched for it due to queue limits, we can debug the cause from
UI by checking queue information.
For instance, if AM cannot be launched, we can check "Max Application Master
Resources Per User" and "Max Application Master Resources" to ascertain if
enough resources are available to launch AM.
Would information shown in 2.7.0 Scheduler page be enough to debug the cause ?
> 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)
