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 C20A711C62 for ; Thu, 1 May 2014 13:26:35 +0000 (UTC) Received: (qmail 99838 invoked by uid 500); 1 May 2014 13:26:32 -0000 Delivered-To: apmail-hadoop-yarn-issues-archive@hadoop.apache.org Received: (qmail 99739 invoked by uid 500); 1 May 2014 13:26:26 -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 99606 invoked by uid 99); 1 May 2014 13:26:17 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 01 May 2014 13:26:17 +0000 Date: Thu, 1 May 2014 13:26:17 +0000 (UTC) From: "Tsuyoshi OZAWA (JIRA)" To: yarn-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Assigned] (YARN-2013) The diagnostics is always the ExitCodeException stack when the container 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-2013?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tsuyoshi OZAWA reassigned YARN-2013: ------------------------------------ Assignee: Tsuyoshi OZAWA > The diagnostics is always the ExitCodeException stack when the container crashes > -------------------------------------------------------------------------------- > > Key: YARN-2013 > URL: https://issues.apache.org/jira/browse/YARN-2013 > Project: Hadoop YARN > Issue Type: Bug > Components: nodemanager > Reporter: Zhijie Shen > Assignee: Tsuyoshi OZAWA > > When a container crashes, ExitCodeException will be thrown from Shell. Default/LinuxContainerExecutor captures the exception, put the exception stack into the diagnostic. Therefore, the exception stack is always the same. > {code} > String diagnostics = "Exception from container-launch: \n" > + StringUtils.stringifyException(e) + "\n" + shExec.getOutput(); > container.handle(new ContainerDiagnosticsUpdateEvent(containerId, > diagnostics)); > {code} > In addition, it seems that the exception always has a empty message as there's no message from stderr. Hence the diagnostics is not of much use for users to analyze the reason of container crash. -- This message was sent by Atlassian JIRA (v6.2#6252)