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 516B1FA07 for ; Tue, 16 Apr 2013 18:55:16 +0000 (UTC) Received: (qmail 23324 invoked by uid 500); 16 Apr 2013 18:55:16 -0000 Delivered-To: apmail-hadoop-yarn-issues-archive@hadoop.apache.org Received: (qmail 23303 invoked by uid 500); 16 Apr 2013 18:55:16 -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 23294 invoked by uid 99); 16 Apr 2013 18:55:16 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 16 Apr 2013 18:55:16 +0000 Date: Tue, 16 Apr 2013 18:55:16 +0000 (UTC) From: "Sandy Ryza (JIRA)" To: yarn-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (YARN-560) If AM fails due to overrunning resource limits, error not visible through UI sometimes 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-560?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13633183#comment-13633183 ] Sandy Ryza commented on YARN-560: --------------------------------- Ravi, The patch looks good to me. Nit: can you use block comments ( /** ... */ ) instead of single line comments over the tests? > If AM fails due to overrunning resource limits, error not visible through UI sometimes > -------------------------------------------------------------------------------------- > > Key: YARN-560 > URL: https://issues.apache.org/jira/browse/YARN-560 > Project: Hadoop YARN > Issue Type: Bug > Affects Versions: 0.23.3, 2.0.0-alpha > Reporter: Todd Lipcon > Assignee: Ravi Prakash > Priority: Minor > Labels: usability > Attachments: MAPREDUCE-3949.patch, YARN-560.patch > > > I had a case where an MR AM eclipsed the configured memory limit. This caused the AM's container to get killed, but nowhere accessible through the web UI showed these diagnostics. I had to go view the NM's logs via ssh before I could figure out what had happened to my application. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira