From yarn-issues-return-139980-apmail-hadoop-yarn-issues-archive=hadoop.apache.org@hadoop.apache.org Sat Mar 17 21:53:08 2018 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 3A27B18031 for ; Sat, 17 Mar 2018 21:53:08 +0000 (UTC) Received: (qmail 25252 invoked by uid 500); 17 Mar 2018 21:53:03 -0000 Delivered-To: apmail-hadoop-yarn-issues-archive@hadoop.apache.org Received: (qmail 25162 invoked by uid 500); 17 Mar 2018 21:53:03 -0000 Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list yarn-issues@hadoop.apache.org Received: (qmail 25146 invoked by uid 99); 17 Mar 2018 21:53:02 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 17 Mar 2018 21:53:02 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id 8A2B5180457 for ; Sat, 17 Mar 2018 21:53:02 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -109.511 X-Spam-Level: X-Spam-Status: No, score=-109.511 tagged_above=-999 required=6.31 tests=[ENV_AND_HDR_SPF_MATCH=-0.5, KAM_ASCII_DIVIDERS=0.8, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_SPF_WL=-7.5, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id JYGBm0HpGmcC for ; Sat, 17 Mar 2018 21:53:01 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id 1F66E5F401 for ; Sat, 17 Mar 2018 21:53:01 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 53C66E0185 for ; Sat, 17 Mar 2018 21:53:00 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 10EB82128E for ; Sat, 17 Mar 2018 21:53:00 +0000 (UTC) Date: Sat, 17 Mar 2018 21:53:00 +0000 (UTC) From: "Shane Kumpf (JIRA)" To: yarn-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (YARN-8043) Add the exception message for failed launches running under LCE MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/YARN-8043?page=3Dcom.atlassian.= jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D16403= 744#comment-16403744 ]=20 Shane Kumpf commented on YARN-8043: ----------------------------------- I believe the intent for the {{output}} and {{errorOutput}} fields in {{Con= tainerExecutionException}} were meant to represent stdout/stderr for a shel= l command.The easy fix here is to add a {{getMessage}} call to the diagnost= ics output and clearly display what "errorOutput" is. I'll put up a patch t= hat does that. > Add the exception message for failed launches running under LCE > --------------------------------------------------------------- > > Key: YARN-8043 > URL: https://issues.apache.org/jira/browse/YARN-8043 > Project: Hadoop YARN > Issue Type: Bug > Reporter: Shane Kumpf > Priority: Major > > If a {{ContainerExecutionException}} is thrown during container launch un= der LCE information is added to the diagnostics for the container regarding= the failure.=C2=A0The diagnostic's output includes the container id, exit = code, "error output" and "shell output", with the expectation that the rele= vant exception details are in the "error output".=C2=A0 > {{ContainerExecutionException}} has several constructors, with the most c= ommonly used being the one that accepts a String. This form does not put th= e exception details into the "error output". This makes it difficult for th= e user to troubleshoot the failure. -- This message was sent by Atlassian JIRA (v7.6.3#76005) --------------------------------------------------------------------- To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org For additional commands, e-mail: yarn-issues-help@hadoop.apache.org