Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Sun, 16 Oct 2011 02:20:13 +0000 (UTC)
From: "Ted Yu (Commented) (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: 
 <130894733.17940.1318731613367.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1478714648.13507.1318215991144.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (HBASE-4562) When split doing
 offlineParentInMeta encounters error, it'll cause data loss
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Ted Yu commented on HBASE-4562:
-------------------------------

+1 on patches.
                
> When split doing offlineParentInMeta encounters error, it'll cause data loss
> ----------------------------------------------------------------------------
>
>                 Key: HBASE-4562
>                 URL: https://issues.apache.org/jira/browse/HBASE-4562
>             Project: HBase
>          Issue Type: Bug
>          Components: regionserver
>    Affects Versions: 0.90.4
>            Reporter: bluedavy
>            Priority: Blocker
>             Fix For: 0.90.5
>
>         Attachments: HBASE-4562-0.90.patch, HBASE-4562-0.92.patch, HBASE-4562-trunk.patch, test-4562-0.90.txt, test-4562-0.92.txt, test-4562-trunk.txt
>
>
> Follow below steps to replay the problem:
> 1. change the SplitTransaction.java as below,just like mock the timeout error.
>    {code:title=SplitTransaction.java|borderStyle=solid}
>       if (!testing) {
>         MetaEditor.offlineParentInMeta(server.getCatalogTracker(),
>            this.parent.getRegionInfo(), a.getRegionInfo(), b.getRegionInfo());
>         throw new IOException("some unexpected error in split");
>       }
>    {code} 
> 2. update the regionserver code,restart;
> 3. create a table & put some data to the table;
> 4. split the table;
> 5. kill the regionserver hosted the table;
> 6. wait some time after master ServerShutdownHandler.process execute,then scan the table,u'll find the data wrote before lost.
> We can fix the bug just use the patch.

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