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 D904B18806 for ; Thu, 10 Sep 2015 07:42:46 +0000 (UTC) Received: (qmail 64397 invoked by uid 500); 10 Sep 2015 07:42:46 -0000 Delivered-To: apmail-hadoop-yarn-issues-archive@hadoop.apache.org Received: (qmail 64351 invoked by uid 500); 10 Sep 2015 07:42:46 -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 64338 invoked by uid 99); 10 Sep 2015 07:42:46 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 10 Sep 2015 07:42:46 +0000 Date: Thu, 10 Sep 2015 07:42:46 +0000 (UTC) From: "Hadoop QA (JIRA)" To: yarn-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (YARN-4111) Killed application diagnostics message should be set rather having static mesage 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-4111?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14738348#comment-14738348 ] Hadoop QA commented on YARN-4111: --------------------------------- \\ \\ | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote || Subsystem || Runtime || Comment || | {color:blue}0{color} | pre-patch | 16m 39s | Pre-patch trunk compilation is healthy. | | {color:green}+1{color} | @author | 0m 0s | The patch does not contain any @author tags. | | {color:green}+1{color} | tests included | 0m 0s | The patch appears to include 3 new or modified test files. | | {color:green}+1{color} | javac | 7m 56s | There were no new javac warning messages. | | {color:green}+1{color} | javadoc | 9m 52s | There were no new javadoc warning messages. | | {color:green}+1{color} | release audit | 0m 22s | The applied patch does not increase the total number of release audit warnings. | | {color:red}-1{color} | checkstyle | 0m 52s | The applied patch generated 1 new checkstyle issues (total was 299, now 300). | | {color:green}+1{color} | whitespace | 0m 2s | The patch has no lines that end in whitespace. | | {color:green}+1{color} | install | 1m 27s | mvn install still works. | | {color:green}+1{color} | eclipse:eclipse | 0m 34s | The patch built with eclipse:eclipse. | | {color:green}+1{color} | findbugs | 1m 29s | The patch does not introduce any new Findbugs (version 3.0.0) warnings. | | {color:green}+1{color} | yarn tests | 54m 19s | Tests passed in hadoop-yarn-server-resourcemanager. | | | | 93m 35s | | \\ \\ || Subsystem || Report/Notes || | Patch URL | http://issues.apache.org/jira/secure/attachment/12755071/YARN-4111_2.patch | | Optional Tests | javadoc javac unit findbugs checkstyle | | git revision | trunk / f153710 | | checkstyle | https://builds.apache.org/job/PreCommit-YARN-Build/9075/artifact/patchprocess/diffcheckstylehadoop-yarn-server-resourcemanager.txt | | hadoop-yarn-server-resourcemanager test log | https://builds.apache.org/job/PreCommit-YARN-Build/9075/artifact/patchprocess/testrun_hadoop-yarn-server-resourcemanager.txt | | Test Results | https://builds.apache.org/job/PreCommit-YARN-Build/9075/testReport/ | | Java | 1.7.0_55 | | uname | Linux asf905.gq1.ygridcore.net 3.13.0-36-lowlatency #63-Ubuntu SMP PREEMPT Wed Sep 3 21:56:12 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux | | Console output | https://builds.apache.org/job/PreCommit-YARN-Build/9075/console | This message was automatically generated. > Killed application diagnostics message should be set rather having static mesage > -------------------------------------------------------------------------------- > > Key: YARN-4111 > URL: https://issues.apache.org/jira/browse/YARN-4111 > Project: Hadoop YARN > Issue Type: Improvement > Components: resourcemanager > Reporter: Rohith Sharma K S > Assignee: nijel > Attachments: YARN-4111_1.patch, YARN-4111_2.patch > > > Application can be killed either by *user via ClientRMService* OR *from scheduler*. Currently diagnostic message is set statically i.e {{Application killed by user.}} neverthless of application killed by scheduler. This brings the confusion to the user after application is Killed that he did not kill application at all but diagnostic message depicts that 'application is killed by user'. > It would be useful if the diagnostic message are different for each cause of KILL. -- This message was sent by Atlassian JIRA (v6.3.4#6332)