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 2016/02/25 20:49:18 UTC

[jira] [Commented] (HBASE-15331) HBase Backup/Restore Phase 2: Optimized Restore operation

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

Vladimir Rodionov commented on HBASE-15331:
-------------------------------------------

Make sure we support physical table layout change (except delete/truncate in this phase 2).

> HBase Backup/Restore Phase 2: Optimized Restore operation
> ---------------------------------------------------------
>
>                 Key: HBASE-15331
>                 URL: https://issues.apache.org/jira/browse/HBASE-15331
>             Project: HBase
>          Issue Type: Improvement
>            Reporter: Vladimir Rodionov
>            Assignee: Vladimir Rodionov
>
> The current implementation for restore uses WALReplay M/R job. This has performance and stability problems, since it uses HBase client API to insert data. We have to migrate to bulk load approach: generate hfiles directly from snapshot and incremental images.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)