Return-Path: X-Original-To: apmail-hbase-issues-archive@www.apache.org Delivered-To: apmail-hbase-issues-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id AD296D5E5 for ; Thu, 11 Oct 2012 23:45:03 +0000 (UTC) Received: (qmail 39852 invoked by uid 500); 11 Oct 2012 23:45:03 -0000 Delivered-To: apmail-hbase-issues-archive@hbase.apache.org Received: (qmail 39817 invoked by uid 500); 11 Oct 2012 23:45:03 -0000 Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list issues@hbase.apache.org Received: (qmail 39806 invoked by uid 99); 11 Oct 2012 23:45:03 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 11 Oct 2012 23:45:03 +0000 Date: Thu, 11 Oct 2012 23:45:03 +0000 (UTC) From: "Hadoop QA (JIRA)" To: issues@hbase.apache.org Message-ID: <296597495.33911.1349999103426.JavaMail.jiratomcat@arcas> In-Reply-To: <430637964.32692.1349982063615.JavaMail.jiratomcat@arcas> Subject: [jira] [Commented] (HBASE-6979) recovered.edits file should not break distributed log splitting 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/HBASE-6979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13474634#comment-13474634 ] Hadoop QA commented on HBASE-6979: ---------------------------------- {color:red}-1 overall{color}. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12548816/trunk-6979.patch against trunk revision . {color:green}+1 @author{color}. The patch does not contain any @author tags. {color:green}+1 tests included{color}. The patch appears to include 3 new or modified tests. {color:green}+1 hadoop2.0{color}. The patch compiles against the hadoop 2.0 profile. {color:red}-1 javadoc{color}. The javadoc tool appears to have generated 81 warning messages. {color:green}+1 javac{color}. The applied patch does not increase the total number of javac compiler warnings. {color:red}-1 findbugs{color}. The patch appears to introduce 5 new Findbugs (version 1.3.9) 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: org.apache.hadoop.hbase.io.hfile.TestForceCacheImportantBlocks org.apache.hadoop.hbase.backup.example.TestZooKeeperTableArchiveClient Test results: https://builds.apache.org/job/PreCommit-HBASE-Build/3036//testReport/ Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/3036//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop2-compat.html Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/3036//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-server.html Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/3036//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop1-compat.html Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/3036//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-common.html Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/3036//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop-compat.html Console output: https://builds.apache.org/job/PreCommit-HBASE-Build/3036//console This message is automatically generated. > recovered.edits file should not break distributed log splitting > --------------------------------------------------------------- > > Key: HBASE-6979 > URL: https://issues.apache.org/jira/browse/HBASE-6979 > Project: HBase > Issue Type: Improvement > Components: master > Reporter: Jimmy Xiang > Assignee: Jimmy Xiang > Attachments: trunk-6979.patch > > > Distributed log splitting fails in creating the recovered.edits folder during upgrade because there is a file called recovered.edits there. > Instead of checking if the patch exists, we need to check if it exists and is a path. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira