[
https://issues.apache.org/jira/browse/HBASE-13737?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14554217#comment-14554217
]
Ashutosh Jindal commented on HBASE-13737:
-----------------------------------------
Non mob data is intact.
As per initial analysis, the problem is in HFileLinkCleaner.isFileDeletable .
Once we clone a snapshot, the data is moved to "/hbase/archive/" .HFileCleaner
checks for back reference for all the files in "/hbase/archive/" dir but it
checks for back references in rootDir i.e. /hbase. In case of MOB data, cleaner
will not find it in rootDir and will delete the link. Here we need to check in
for references in /hbase/mobdir also.
> [HBase MOB] MOBTable cloned from a snapshot leads to data loss, when that
> actual snapshot and main table is deleted.
> --------------------------------------------------------------------------------------------------------------------
>
> Key: HBASE-13737
> URL: https://issues.apache.org/jira/browse/HBASE-13737
> Project: HBase
> Issue Type: Bug
> Components: mob
> Affects Versions: hbase-11339
> Reporter: Y. SREENIVASULU REDDY
> Assignee: Ashutosh Jindal
> Priority: Critical
> Fix For: hbase-11339
>
>
> clone snapshot on mob feature leads to data loss for mob data.
> steps to reproduce:
> ===============
> 1. created MOB table with two column families like "mobcf" (mob is enabled)
> and "norcf"
> 2. insert mob data and normal data at a time into the table.
> 3. scan the MOB table.
> 4. take snapshot by specifying the table name.
> 5. clone the snapshot by specifying the new table name.
> 6. check the new table is created or not and try scan for the new table which
> have both mob data and normal data should give back to the client.
> 7. delete the snapshot which done in step 4.
> 8. delete the main table which done in step 1.
> 9. Now scan the new table again.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
