You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-issues@hadoop.apache.org by "Akira AJISAKA (JIRA)" <ji...@apache.org> on 2016/01/06 06:43:40 UTC
[jira] [Commented] (YARN-3946) Update exact reason as to why a
submitted app is in ACCEPTED state to app's diagnostic message
[ https://issues.apache.org/jira/browse/YARN-3946?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15085012#comment-15085012 ]
Akira AJISAKA commented on YARN-3946:
-------------------------------------
Hi [~Naganarasimha] and [~leftnoteasy], TestNetworkedJob is failing after this issue. Would you please review the patch in MAPREDUCE-6579?
> Update exact reason as to why a submitted app is in ACCEPTED state to app's diagnostic message
> ----------------------------------------------------------------------------------------------
>
> 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
> Fix For: 2.8.0
>
> 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)