You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "terry zhang (JIRA)" <ji...@apache.org> on 2013/08/14 12:36:48 UTC

[jira] [Updated] (HBASE-9214) CatalogJanitor delete region info in Meta during Restore snapshot

     [ https://issues.apache.org/jira/browse/HBASE-9214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

terry zhang updated HBASE-9214:
-------------------------------

    Description: 
Today I meet a issue during restore snapshot. It can be reproduce in step below:

1. Table t1 create a Snapshot s1 successfully
2. region r1 in t1 split 
3. CatalogJanitor Chore begin to work and found daughter  do not have reference , so r1 can be deleted
4. restore snapshot s1 . RestoreSnapshotHelper add region r1 to meta table
5.  CatalogJanitor delete r1 region info in meta which RestoreSnapshotHelper just inserted .
6. restore snapshot finished.

Then we can found there is a hole in t1 after restore snapshot. Data loss.


    
> CatalogJanitor delete region info in Meta during Restore snapshot
> -----------------------------------------------------------------
>
>                 Key: HBASE-9214
>                 URL: https://issues.apache.org/jira/browse/HBASE-9214
>             Project: HBase
>          Issue Type: Bug
>          Components: master
>    Affects Versions: 0.94.10
>            Reporter: terry zhang
>
> Today I meet a issue during restore snapshot. It can be reproduce in step below:
> 1. Table t1 create a Snapshot s1 successfully
> 2. region r1 in t1 split 
> 3. CatalogJanitor Chore begin to work and found daughter  do not have reference , so r1 can be deleted
> 4. restore snapshot s1 . RestoreSnapshotHelper add region r1 to meta table
> 5.  CatalogJanitor delete r1 region info in meta which RestoreSnapshotHelper just inserted .
> 6. restore snapshot finished.
> Then we can found there is a hole in t1 after restore snapshot. Data loss.

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