Mailing-List: contact dev-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hbase.apache.org
Date: Fri, 11 Mar 2016 19:24:39 +0000 (UTC)
From: "Vladimir Rodionov (JIRA)" <jira@apache.org>
To: dev@hbase.apache.org
Message-ID: <JIRA.12944639.1456429651000.1415.1457724279037@Atlassian.JIRA>
In-Reply-To: <JIRA.12944639.1456429651000@Atlassian.JIRA>
References: <JIRA.12944639.1456429651000@Atlassian.JIRA>
 <JIRA.12944639.1456429651696@arcas>
Subject: [jira] [Resolved] (HBASE-15331) HBase Backup/Restore Phase 2:
 Optimized Restore operation
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/HBASE-15331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Vladimir Rodionov resolved HBASE-15331.
---------------------------------------
    Resolution: Fixed

The work continues in HBASE-15448

> 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. We run separate M/R job for every backup image between last FULL backup and current incremental backup we restore to and for every table in the list (image). If we have 10 tables and 30 days of incremental backup images - this results in 30x10 = 300 M/R jobs. MUST be optimized.


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