Return-Path: 
 <issues-return-21435-apmail-hbase-issues-archive=hbase.apache.org@hbase.apache.org>
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 B6C017426
	for <apmail-hbase-issues-archive@www.apache.org>;
 Tue, 11 Oct 2011 01:06:51 +0000 (UTC)
Received: (qmail 89537 invoked by uid 500); 11 Oct 2011 01:06:51 -0000
Delivered-To: apmail-hbase-issues-archive@hbase.apache.org
Received: (qmail 89512 invoked by uid 500); 11 Oct 2011 01:06:51 -0000
Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:issues-help@hbase.apache.org>
List-Unsubscribe: <mailto:issues-unsubscribe@hbase.apache.org>
List-Post: <mailto:issues@hbase.apache.org>
List-Id: <issues.hbase.apache.org>
Delivered-To: mailing list issues@hbase.apache.org
Received: (qmail 89504 invoked by uid 99); 11 Oct 2011 01:06:51 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 11 Oct 2011 01:06:51 +0000
X-ASF-Spam-Status: No, hits=-2000.5 required=5.0
	tests=ALL_TRUSTED,RP_MATCHES_RCVD
X-Spam-Check-By: apache.org
Received: from [140.211.11.116] (HELO hel.zones.apache.org) (140.211.11.116)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 11 Oct 2011 01:06:50 +0000
Received: from hel.zones.apache.org (hel.zones.apache.org [140.211.11.116])
	by hel.zones.apache.org (Postfix) with ESMTP id C4D3B301C57
	for <issues@hbase.apache.org>; Tue, 11 Oct 2011 01:06:29 +0000 (UTC)
Date: Tue, 11 Oct 2011 01:06:29 +0000 (UTC)
From: "bluedavy (Commented) (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: 
 <904244142.17390.1318295189807.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <2109502295.13523.1318216470010.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (HBASE-4563) When split doing
 this.parent.close(false) occurs error,it'll cause the splited region cann't
 write & read
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-4563?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13124635#comment-13124635 ] 

bluedavy commented on HBASE-4563:
---------------------------------

@Ted Yu
Yes,:),I'll change it & attach the patch again.
                
> When split doing this.parent.close(false) occurs error,it'll cause the splited region cann't write & read
> ---------------------------------------------------------------------------------------------------------
>
>                 Key: HBASE-4563
>                 URL: https://issues.apache.org/jira/browse/HBASE-4563
>             Project: HBase
>          Issue Type: Bug
>          Components: regionserver
>    Affects Versions: 0.90.4
>            Reporter: bluedavy
>            Priority: Blocker
>             Fix For: 0.90.5
>
>         Attachments: HBASE-4563-test.report.txt, HBASE-4563.patch
>
>
> Follow below steps to replay the problem:
> 1. change the SplitTransaction.java as below,just like mock the hdfs error.
>    {code:title=SplitTransaction.java|borderStyle=solid}
>       List<StoreFile> hstoreFilesToSplit = this.parent.close(false);
>       throw new IOException("some unexpected error in close store files");
>    {code} 
> 2. update the regionserver code,restart;
> 3. create a table & put some data to the table;
> 4. split the table;
> 5. scan the table,then it'll fail.
> We can fix the bug just use below code:
> {code:title=SplitTransaction.java|borderStyle=solid}
>       List<StoreFile> hstoreFilesToSplit = null;
>       try{
>           hstoreFilesToSplit = this.parent.close(false);
>       }
>       catch(IOException  e){
>           this.journal.add(JournalEntry.CLOSED_PARENT_REGION);
>           throw e;
>       }
> {code} 

--
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