Return-Path: X-Original-To: apmail-hadoop-yarn-issues-archive@minotaur.apache.org Delivered-To: apmail-hadoop-yarn-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id C5CFE188C2 for ; Thu, 3 Dec 2015 19:16:14 +0000 (UTC) Received: (qmail 16005 invoked by uid 500); 3 Dec 2015 19:16:11 -0000 Delivered-To: apmail-hadoop-yarn-issues-archive@hadoop.apache.org Received: (qmail 15909 invoked by uid 500); 3 Dec 2015 19:16:11 -0000 Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: yarn-issues@hadoop.apache.org Delivered-To: mailing list yarn-issues@hadoop.apache.org Received: (qmail 15825 invoked by uid 99); 3 Dec 2015 19:16:11 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 03 Dec 2015 19:16:11 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id 336002C1F75 for ; Thu, 3 Dec 2015 19:16:11 +0000 (UTC) Date: Thu, 3 Dec 2015 19:16:11 +0000 (UTC) From: "Naganarasimha G R (JIRA)" To: yarn-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (YARN-3946) Allow fetching exact reason as to why a submitted app is in ACCEPTED state in CS MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/YARN-3946?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15038381#comment-15038381 ] Naganarasimha G R commented on YARN-3946: ----------------------------------------- Hi [~wangda], Some of the test failures seems to be related to the patch also would merge {{checkAndUpdateAMContainerDiagnostics}} and {{updateAMContainerDiagnostics}} with additional parameter rather than another method. Will upload a new patch at the earliest. > 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, YARN-3946.v1.005.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)