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 9C8BD1826E for ; Wed, 29 Jul 2015 16:34:05 +0000 (UTC) Received: (qmail 91911 invoked by uid 500); 29 Jul 2015 16:34:05 -0000 Delivered-To: apmail-hadoop-yarn-issues-archive@hadoop.apache.org Received: (qmail 91869 invoked by uid 500); 29 Jul 2015 16:34:05 -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 91854 invoked by uid 99); 29 Jul 2015 16:34:05 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 29 Jul 2015 16:34:05 +0000 Date: Wed, 29 Jul 2015 16:34:05 +0000 (UTC) From: "Bibin A Chundatt (JIRA)" To: yarn-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (YARN-3989) Show messages only for NodeLabel commmands in RMAdminCLI 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-3989?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14646361#comment-14646361 ] Bibin A Chundatt commented on YARN-3989: ---------------------------------------- [~sunilg] and [~Naganarasimha] Currently only NodeLabel i would like to put in scope for this Jira.Other commands makes it more complicated. Few commands as [~sunilg] pointed out. # addToCluserNodeLabels # removeFromClusterNodeLabels # replaceLabelsOnNode Its a huge stack trace which is shown in console and from trace it becomes very difficult to get the actual error message.Most of the cases only direct messages are intended for users not full stack trace. So as of now will define scope only to Nodelabel commands in this jira. > Show messages only for NodeLabel commmands in RMAdminCLI > -------------------------------------------------------- > > Key: YARN-3989 > URL: https://issues.apache.org/jira/browse/YARN-3989 > Project: Hadoop YARN > Issue Type: Bug > Reporter: Bibin A Chundatt > Assignee: Bibin A Chundatt > Priority: Minor > > Currently for nodelabel command execution failure full exception stacktrace is shown. This jira is to handle exceptions and show only messages. > As per the discussion in YARN-3963 > [~sunilg] > {quote} > As I see it, I can see full exception stack trace in client side in this case (also in case of other commands too) and its too verbose. I think we can make its compact and n it will be more easily readable. > {quote} -- This message was sent by Atlassian JIRA (v6.3.4#6332)