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

Matteo Bertozzi updated HBASE-8760:
-----------------------------------

    Attachment: HBASE-8760-v4.patch
                HBASE-8760-0.94-v4.patch

v4 should be the final one.

easy way to test this stuff put a return null inside the HStore.compaction() to 
avoid compactions. Then run the stuff above in the hbase shell to create a 
table, snapshot, clone and a clone of clone.. Then remove the original table 
and way the archiver to do the job. Play with enable/disable to test the load 
unload cloned table and verify that the files are still readable. Also check 
the /hbase dir to look if all the expected files are there.

I'm not able to constantly reproduce the HFileLink problem and I haven't seen 
the problem after this patch, but the symptom was an exception during the 
enable of a cloned table with a link resolving to /hbase/.data/tableName 
instead of /hbase/.data/default/tableName, basically the "dafault" namespace 
dir was not there. Anyway this will be another jira
                
> possible loss of data in snapshot taken after region split
> ----------------------------------------------------------
>
>                 Key: HBASE-8760
>                 URL: https://issues.apache.org/jira/browse/HBASE-8760
>             Project: HBase
>          Issue Type: Bug
>          Components: snapshots
>    Affects Versions: 0.94.8, 0.95.1
>            Reporter: Jerry He
>             Fix For: 0.98.0, 0.95.2, 0.94.12
>
>         Attachments: HBase-8760-0.94.8.patch, HBase-8760-0.94.8-v1.patch, 
> HBASE-8760-0.94-v4.patch, HBASE-8760-thz-v0.patch, HBASE-8760-thz-v1.patch, 
> HBASE-8760-thz-v2.patch, HBASE-8760-thz-v3.patch, HBASE-8760-v4.patch
>
>
> Right after a region split but before the daughter regions are compacted, we 
> have two daughter regions containing Reference files to the parent hfiles.
> If we take snapshot right at the moment, the snapshot will succeed, but it 
> will only contain the daughter Reference files. Since there is no hold on the 
> parent hfiles, they will be deleted by the HFile Cleaner after they are no 
> longer needed by the daughter regions soon after.
> A minimum we need to do is the keep these parent hfiles from being deleted. 

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

Reply via email to