You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Vladimir Rodionov (JIRA)" <ji...@apache.org> on 2018/02/09 23:00:00 UTC

[jira] [Comment Edited] (HBASE-17825) Backup: further optimizations

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

Vladimir Rodionov edited comment on HBASE-17825 at 2/9/18 10:59 PM:
--------------------------------------------------------------------

{quote}
When false is returned, some files would be deleted while some are left. Is this desirable? 
{quote}

This needs to be added to FT Jira. We need to restore not only meta in case of failure but physical data as well. 

That is the separate issue: HBASE-19969


was (Author: vrodionov):
{quote}
When false is returned, some files would be deleted while some are left. Is this desirable? 
{quote}

This needs to be added to FT Jira. We need to restore not only meta in case of failure but physical data as well. 

> Backup: further optimizations
> -----------------------------
>
>                 Key: HBASE-17825
>                 URL: https://issues.apache.org/jira/browse/HBASE-17825
>             Project: HBase
>          Issue Type: Improvement
>            Reporter: Vladimir Rodionov
>            Assignee: Vladimir Rodionov
>            Priority: Critical
>              Labels: backup
>             Fix For: 3.0.0
>
>         Attachments: HBASE-17825-v1.patch
>
>
> Some phases of backup and restore can be optimized:
> # WALPlayer support for multiple tables
> # Run DistCp once per all tables during backup/restore
> The eventual goal:
> # 2 M/R jobs per backup/restore



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)