[
https://issues.apache.org/jira/browse/HBASE-15862?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15328885#comment-15328885
]
Vladimir Rodionov commented on HBASE-15862:
-------------------------------------------
Snapshot restore works with arbitrary boundaries.
If we select truncate option:
First full backup restore can take a long time, because, bulk load tool will
need to split (align) all HFiles to all boundaries before pushing them to a
cluster. The second step (M/R job to load all WAL files) will finish pretty
quickly and no region splits will be afterwords.
If we select delete option:
First full backup restore will finish quickly, second step will finish quickly
as well, but we will have a lot of region splits and major compaction when
restore finishes.
I vote for truncate as an interim solution.
> Backup - Delete- Restore does not restore deleted data
> ------------------------------------------------------
>
> Key: HBASE-15862
> URL: https://issues.apache.org/jira/browse/HBASE-15862
> Project: HBase
> Issue Type: Bug
> Affects Versions: 2.0.0
> Reporter: Vladimir Rodionov
> Assignee: Vladimir Rodionov
> Labels: backup
> Fix For: 2.0.0
>
> Attachments: HBASE-15862-v1.patch, HBASE-15862-v2.patch,
> HBASE-15862-v3.patch
>
>
> This was discovered during testing. If we delete row after full backup and
> perform immediately restore, the deleted row still remains deleted.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
