You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Jonathan Hsieh (JIRA)" <ji...@apache.org> on 2013/12/09 22:00:07 UTC
[jira] [Commented] (HBASE-10111) Verify that a snapshot is not
corrupted before restoring it
[ https://issues.apache.org/jira/browse/HBASE-10111?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13843546#comment-13843546 ]
Jonathan Hsieh commented on HBASE-10111:
----------------------------------------
+1 lgtm.
> Verify that a snapshot is not corrupted before restoring it
> -----------------------------------------------------------
>
> Key: HBASE-10111
> URL: https://issues.apache.org/jira/browse/HBASE-10111
> Project: HBase
> Issue Type: Bug
> Components: snapshots
> Affects Versions: 0.98.0, 0.96.0, 0.94.14
> Reporter: Matteo Bertozzi
> Assignee: Matteo Bertozzi
> Priority: Minor
> Fix For: 0.98.0, 0.96.1
>
> Attachments: HBASE-10111-v0.patch
>
>
> To avoid assigning/opening regions with missing files, verify that the snapshot is not corrupted before restoring/cloning it.
> In 96 a corrupted file in a region is "not a problem" since the assignment will give up after awhile.
> In 94 having a corrupted file in a region means looping forever, on "enable", until manual intervention. (Easy way to test this is create a table, disable it, add a corrupted reference file and enable the table to start looping: you can use echo "foo" > aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa.aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa)
--
This message was sent by Atlassian JIRA
(v6.1.4#6159)