[
https://issues.apache.org/jira/browse/HBASE-17852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16257580#comment-16257580
]
Vladimir Rodionov commented on HBASE-17852:
-------------------------------------------
{quote}
The snapshot/restore of a whole system table strikes me as a bunch of moving
parts.
{quote}
That is only one backup system table.
{quote}
I have to ask why we got such an extreme?
{quote}
What is so extreme here? Snapshot of a system table? I consider this approach
much more simple and elegant than
others?
{quote}
During restore, all clients are frozen out or something so they can't pollute
the restored version?
{quote}
Yes. During table restore operation, all clients (of this table) must be
stopped. In theory, this is not a hard requirement - it is just an advice. But,
we truncate table, before restore and this, definitely, may affect unexpectedly
incoming writes. Any database system, which allows writes to a table during
restore of a table?
Stack, if you have doubts in the implementation, I suggest you to go over code
and find places where you think the code has issues.
> 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)
