[
https://issues.apache.org/jira/browse/HBASE-17852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16260212#comment-16260212
]
Vladimir Rodionov commented on HBASE-17852:
-------------------------------------------
{quote}
My gut reaction is that the number of backups which would need to be retained
in the system (e.g. rows in the hbase backup "system" table) would have to be
quite large to even grow beyond a single region (many thousands to millions).
As such, the snapshot restore isn't much more than grabbing the write lock and
replacing some one data file and some Region metadata. This is on my list today
to investigate confirm.
{quote}
Yes, [~elserj], you are right. Backup system table for vast majority of
deployments will fit a single region. It is a metadata - not a data. Therefore,
creation of snapshot and restoring from snapshot is a very lightweight
operation. That is was a major reason I have chosen rollback-via-snapshot
approach.
> Add Fault tolerance to HBASE-14417 (Support bulk loaded files in incremental
> backup)
> ------------------------------------------------------------------------------------
>
> Key: HBASE-17852
> URL: https://issues.apache.org/jira/browse/HBASE-17852
> Project: HBase
> Issue Type: Sub-task
> Reporter: Vladimir Rodionov
> Assignee: Vladimir Rodionov
> Fix For: 2.0.0-beta-1
>
> Attachments: HBASE-17852-v1.patch, HBASE-17852-v2.patch,
> HBASE-17852-v3.patch, HBASE-17852-v4.patch, HBASE-17852-v5.patch,
> HBASE-17852-v6.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
