Return-Path: X-Original-To: apmail-hadoop-hdfs-issues-archive@minotaur.apache.org Delivered-To: apmail-hadoop-hdfs-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 6302017650 for ; Wed, 11 Mar 2015 02:07:13 +0000 (UTC) Received: (qmail 79575 invoked by uid 500); 11 Mar 2015 02:06:39 -0000 Delivered-To: apmail-hadoop-hdfs-issues-archive@hadoop.apache.org Received: (qmail 79520 invoked by uid 500); 11 Mar 2015 02:06:38 -0000 Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: hdfs-issues@hadoop.apache.org Delivered-To: mailing list hdfs-issues@hadoop.apache.org Received: (qmail 79505 invoked by uid 99); 11 Mar 2015 02:06:38 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 11 Mar 2015 02:06:38 +0000 Date: Wed, 11 Mar 2015 02:06:38 +0000 (UTC) From: "Hadoop QA (JIRA)" To: hdfs-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HDFS-7894) Rolling upgrade readiness is not updated in jmx until query command is issued. 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/HDFS-7894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14356100#comment-14356100 ] Hadoop QA commented on HDFS-7894: --------------------------------- {color:red}-1 overall{color}. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12703295/HDFS-7894-002.patch against trunk revision 64eb068. {color:green}+1 @author{color}. The patch does not contain any @author tags. {color:red}-1 tests included{color}. The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch. {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:red}-1 core tests{color}. The patch failed these unit tests in hadoop-hdfs-project/hadoop-hdfs: org.apache.hadoop.hdfs.server.namenode.TestFileTruncate The following test timeouts occurred in hadoop-hdfs-project/hadoop-hdfs: org.apache.hadoop.hdfs.server.namenode.ha.TestHAAppend Test results: https://builds.apache.org/job/PreCommit-HDFS-Build/9825//testReport/ Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/9825//console This message is automatically generated. > Rolling upgrade readiness is not updated in jmx until query command is issued. > ------------------------------------------------------------------------------ > > Key: HDFS-7894 > URL: https://issues.apache.org/jira/browse/HDFS-7894 > Project: Hadoop HDFS > Issue Type: Bug > Reporter: Kihwal Lee > Assignee: Brahma Reddy Battula > Priority: Critical > Attachments: HDFS-7894-002.patch, HDFS-7894.patch > > > When a hdfs rolling upgrade is started and a rollback image is created/uploaded, the active NN does not update its {{rollingUpgradeInfo}} until it receives a query command via RPC. This results in inconsistent info being showing up in the web UI and its jmx page. -- This message was sent by Atlassian JIRA (v6.3.4#6332)