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 C40CF11A62 for ; Tue, 8 Jul 2014 17:56:06 +0000 (UTC) Received: (qmail 44570 invoked by uid 500); 8 Jul 2014 17:56:06 -0000 Delivered-To: apmail-hadoop-yarn-issues-archive@hadoop.apache.org Received: (qmail 44522 invoked by uid 500); 8 Jul 2014 17:56:06 -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 44508 invoked by uid 99); 8 Jul 2014 17:56:06 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 08 Jul 2014 17:56:06 +0000 Date: Tue, 8 Jul 2014 17:56:06 +0000 (UTC) From: "Li Lu (JIRA)" To: yarn-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (YARN-2242) Improve exception information on AM launch crashes 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-2242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Li Lu updated YARN-2242: ------------------------ Attachment: YARN-2242-070814.patch New patch to add the swallowed diagnostics information back, also reformatted the exception output for easy understanding. Now the exception output contains all original exception information, also a pointer to the logs. Addressed [~stevel@apache.org]'s null URL issue by adding one more branch. > Improve exception information on AM launch crashes > -------------------------------------------------- > > Key: YARN-2242 > URL: https://issues.apache.org/jira/browse/YARN-2242 > Project: Hadoop YARN > Issue Type: Sub-task > Reporter: Li Lu > Assignee: Li Lu > Fix For: 2.6.0 > > Attachments: YARN-2242-070114-1.patch, YARN-2242-070114.patch, YARN-2242-070115-1.patch, YARN-2242-070115-2.patch, YARN-2242-070115.patch, YARN-2242-070814.patch > > > Now on each time AM Container crashes during launch, both the console and the webpage UI only report a ShellExitCodeExecption. This is not only unhelpful, but sometimes confusing. With the help of log aggregator, container logs are actually aggregated, and can be very helpful for debugging. One possible way to improve the whole process is to send a "pointer" to the aggregated logs to the programmer when reporting exception information. -- This message was sent by Atlassian JIRA (v6.2#6252)