Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Date: Mon, 28 Nov 2016 23:48:58 +0000 (UTC)
From: "Yufei Gu (JIRA)" <jira@apache.org>
To: yarn-issues@hadoop.apache.org
Message-ID: <JIRA.13021241.1479324514000.383717.1480376938530@Atlassian.JIRA>
In-Reply-To: <JIRA.13021241.1479324514000@Atlassian.JIRA>
References: <JIRA.13021241.1479324514000@Atlassian.JIRA> <JIRA.13021241.1479324514111@arcas>
Subject: [jira] [Updated] (YARN-5890) FairScheduler should log information
 about AM-resource-usage and max-AM-share for queues
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Mon, 28 Nov 2016 23:49:01 -0000


     [ https://issues.apache.org/jira/browse/YARN-5890?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Yufei Gu updated YARN-5890:
---------------------------
    Attachment: YARN-5890.003.patch

> FairScheduler should log information about AM-resource-usage and max-AM-share for queues
> ----------------------------------------------------------------------------------------
>
>                 Key: YARN-5890
>                 URL: https://issues.apache.org/jira/browse/YARN-5890
>             Project: Hadoop YARN
>          Issue Type: Improvement
>          Components: fairscheduler
>            Reporter: Yufei Gu
>            Assignee: Yufei Gu
>         Attachments: YARN-5890.001.patch, YARN-5890.002.patch, YARN-5890.003.patch
>
>
> There are several cases where jobs in a queue or stuck likely because of maxAMShare. It is hard to debug these issues without any information.
> At the very least, we need to log both AM-resource-usage and max-AM-share for queues. 


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org