hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vladimir Rodionov (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (HBASE-16392) Backup delete fault tolerance
Date Wed, 31 May 2017 21:23:04 GMT

    [ https://issues.apache.org/jira/browse/HBASE-16392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16031939#comment-16031939

Vladimir Rodionov edited comment on HBASE-16392 at 5/31/17 9:22 PM:

That is not feasible. Will require rewriting partially BackupAdminImpl and adding additional
methods to this class exclusively for testing.

The existing unit test does the following

# Full backup of table T
# Snapshot of backup system table - S
# Delete backup T 
# Restore backup system from S
# Verify that we have 1 backup in history
# Manual modification of backup system table to emulate failed delete operation - adding delete
row with list of backup ids
# Runs repair tool
# Verifies that we have 0 backup sessions in a history


was (Author: vrodionov):

> Backup delete fault tolerance
> -----------------------------
>                 Key: HBASE-16392
>                 URL: https://issues.apache.org/jira/browse/HBASE-16392
>             Project: HBase
>          Issue Type: Sub-task
>            Reporter: Vladimir Rodionov
>            Assignee: Vladimir Rodionov
>              Labels: backup
>             Fix For: 2.0.0
>         Attachments: HBASE-16392-v1.patch, HBASE-16392-v2.patch
> Backup delete modified file system and backup system table. We have to make sure that
operation is atomic, durable and isolated.
> Delete operation:
> # Start backup session (this guarantees) that system will be blocked for all backup commands
during delete operation
> # Save list of tables being deleted to system table
> # Before delete operation we take backup system table snapshot  
> # During delete operation we detect any failures and restore backup system table from
snapshot, then finish backup session
> # To guarantee consistency of the data, delete operation MUST be repeated
> # We guarantee that all file delete operations are idempotent, can be repeated multiple
> # Any backup operations will be blocked until consistency is restored
> # To restore consistency, repair command must be executed.
> # Repair command checks if there is failed delete op in a backup system table, and repeats
delete operation

This message was sent by Atlassian JIRA

View raw message