Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Wed, 17 Oct 2012 23:48:04 +0000 (UTC)
From: "Hudson (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <1718852992.61057.1350517684335.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


    [ https://issues.apache.org/jira/browse/HBASE-6979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13478498#comment-13478498 ] 

Hudson commented on HBASE-6979:
-------------------------------

Integrated in HBase-TRUNK-on-Hadoop-2.0.0 #225 (See [https://builds.apache.org/job/HBase-TRUNK-on-Hadoop-2.0.0/225/])
    HBASE-6979 recovered.edits file should not break distributed log splitting (Revision 1399352)

     Result = FAILURE
jxiang : 
Files : 
* /hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/wal/HLogSplitter.java
* /hbase/trunk/hbase-server/src/test/java/org/apache/hadoop/hbase/regionserver/wal/TestHLogSplit.java

                
> 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
>             Fix For: 0.96.0
>
>         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