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 A4B0910B76 for ; Wed, 11 Feb 2015 11:59:12 +0000 (UTC) Received: (qmail 75122 invoked by uid 500); 11 Feb 2015 11:59:12 -0000 Delivered-To: apmail-hadoop-yarn-issues-archive@hadoop.apache.org Received: (qmail 75071 invoked by uid 500); 11 Feb 2015 11:59:12 -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 75059 invoked by uid 99); 11 Feb 2015 11:59:12 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 11 Feb 2015 11:59:12 +0000 Date: Wed, 11 Feb 2015 11:59:12 +0000 (UTC) From: "Hadoop QA (JIRA)" To: yarn-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (YARN-3151) On Failover tracking url wrong in application cli for KILLED application 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-3151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14316105#comment-14316105 ] Hadoop QA commented on YARN-3151: --------------------------------- {color:green}+1 overall{color}. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12698054/0002-YARN-3151.patch against trunk revision a4ceea6. {color:green}+1 @author{color}. The patch does not contain any @author tags. {color:green}+1 tests included{color}. The patch appears to include 2 new or modified test files. {color:green}+1 javac{color}. The applied patch does not increase the total number of javac compiler warnings. {color:green}+1 javadoc{color}. There were no new javadoc warning messages. {color:green}+1 eclipse:eclipse{color}. The patch built with eclipse:eclipse. {color:green}+1 findbugs{color}. The patch does not introduce any new Findbugs (version 2.0.3) warnings. {color:green}+1 release audit{color}. The applied patch does not increase the total number of release audit warnings. {color:green}+1 core tests{color}. The patch passed unit tests in hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager. Test results: https://builds.apache.org/job/PreCommit-YARN-Build/6593//testReport/ Console output: https://builds.apache.org/job/PreCommit-YARN-Build/6593//console This message is automatically generated. > On Failover tracking url wrong in application cli for KILLED application > ------------------------------------------------------------------------ > > Key: YARN-3151 > URL: https://issues.apache.org/jira/browse/YARN-3151 > Project: Hadoop YARN > Issue Type: Bug > Components: client, resourcemanager > Affects Versions: 2.6.0 > Environment: 2 RM HA > Reporter: Bibin A Chundatt > Assignee: Rohith > Priority: Minor > Attachments: 0001-YARN-3151.patch, 0002-YARN-3151.patch, 0002-YARN-3151.patch > > > Run an application and kill the same after starting > Check {color:red} ./yarn application -list -appStates KILLED {color} > (empty line) > {quote} > Application-Id Tracking-URL > application_1423219262738_0001 http://:PORT>/cluster/app/application_1423219262738_0001 > {quote} > Shutdown the active RM1 > Check the same command {color:red} ./yarn application -list -appStates KILLED {color} after RM2 is active > {quote} > Application-Id Tracking-URL > application_1423219262738_0001 null > {quote} > Tracking url for application is shown as null > Expected : Same url before failover should be shown > ApplicationReport .getOriginalTrackingUrl() is null after failover > org.apache.hadoop.yarn.client.cli.ApplicationCLI > listApplications(Set appTypes, > EnumSet appStates) -- This message was sent by Atlassian JIRA (v6.3.4#6332)