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 C53B1DBF0 for ; Tue, 14 Aug 2012 00:55:38 +0000 (UTC) Received: (qmail 39089 invoked by uid 500); 14 Aug 2012 00:55:38 -0000 Delivered-To: apmail-hadoop-hdfs-issues-archive@hadoop.apache.org Received: (qmail 39051 invoked by uid 500); 14 Aug 2012 00:55: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 39040 invoked by uid 99); 14 Aug 2012 00:55:38 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 14 Aug 2012 00:55:38 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id 1CA342C5ACD for ; Tue, 14 Aug 2012 00:55:38 +0000 (UTC) Date: Tue, 14 Aug 2012 11:55:38 +1100 (NCT) From: "Hadoop QA (JIRA)" To: hdfs-issues@hadoop.apache.org Message-ID: <114767425.5477.1344905738118.JavaMail.jiratomcat@arcas> In-Reply-To: <1687714408.15644.1344234422391.JavaMail.jiratomcat@issues-vm> Subject: [jira] [Commented] (HDFS-3765) Namenode INITIALIZESHAREDEDITS should be able to initialize all shared storages 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-3765?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13433797#comment-13433797 ] Hadoop QA commented on HDFS-3765: --------------------------------- -1 overall. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12540746/hdfs-3765.txt against trunk revision . +1 @author. The patch does not contain any @author tags. +1 tests included. The patch appears to include 3 new or modified test files. +1 javac. The applied patch does not increase the total number of javac compiler warnings. +1 javadoc. The javadoc tool did not generate any warning messages. +1 eclipse:eclipse. The patch built with eclipse:eclipse. -1 findbugs. The patch appears to introduce 2 new Findbugs (version 1.3.9) warnings. +1 release audit. The applied patch does not increase the total number of release audit warnings. +1 core tests. The patch passed unit tests in hadoop-common-project/hadoop-common hadoop-hdfs-project/hadoop-hdfs hadoop-hdfs-project/hadoop-hdfs/src/contrib/bkjournal. +1 contrib tests. The patch passed contrib unit tests. Test results: https://builds.apache.org/job/PreCommit-HDFS-Build/2995//testReport/ Findbugs warnings: https://builds.apache.org/job/PreCommit-HDFS-Build/2995//artifact/trunk/patchprocess/newPatchFindbugsWarningshadoop-hdfs.html Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/2995//console This message is automatically generated. > Namenode INITIALIZESHAREDEDITS should be able to initialize all shared storages > ------------------------------------------------------------------------------- > > Key: HDFS-3765 > URL: https://issues.apache.org/jira/browse/HDFS-3765 > Project: Hadoop HDFS > Issue Type: Improvement > Components: ha > Affects Versions: 2.1.0-alpha, 3.0.0 > Reporter: Vinay > Assignee: Vinay > Attachments: HDFS-3765.patch, HDFS-3765.patch, HDFS-3765.patch, hdfs-3765.txt, hdfs-3765.txt, hdfs-3765.txt > > > Currently, NameNode INITIALIZESHAREDEDITS provides ability to copy the edits files to file schema based shared storages when moving cluster from Non-HA environment to HA enabled environment. > This Jira focuses on the following > * Generalizing the logic of copying the edits to new shared storage so that any schema based shared storage can initialized for HA cluster. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira