[
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-thz-v1.patch
Changed my mind again...
the new thz-v1 patch now does this
* The offlined regions are taken as "offline" snapshot
* The the check now verifies that the references have a parent
so,
Quick and simple manual test can be done in this way, and manually verify
/hbase/.hbase-snapshot
{code}
create 'testtb', 'cf'
put 'testtb', 'row0', 'cf:q', 'row0'
put 'testtb', 'row1', 'cf:q', 'row1'
put 'testtb', 'row2', 'cf:q', 'row2'
put 'testtb', 'row3', 'cf:q', 'row3'
put 'testtb', 'row4', 'cf:q', 'row4'
put 'testtb', 'row5', 'cf:q', 'row5'
put 'testtb', 'row6', 'cf:q', 'row6'
flush 'testtb'
split 'testtb', 'row3'
snapshot 'testtb', 'foo'
clone_snapshot 'foo', 'footb'
snapshot 'footb', 'bar'
clone_snapshot 'bar', 'bartb'
scan 'testtb'
scan 'footb'
scan 'bartb'
{code}
> 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-thz-v0.patch, HBASE-8760-thz-v1.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
