Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Tue, 9 Aug 2016 23:43:20 +0000 (UTC)
From: "Devaraj Das (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.12863553.1442010671000.266931.1470786200627@Atlassian.JIRA>
In-Reply-To: <JIRA.12863553.1442010671000@Atlassian.JIRA>
References: <JIRA.12863553.1442010671000@Atlassian.JIRA> <JIRA.12863553.1442010671650@arcas>
Subject: [jira] [Commented] (HBASE-14417) Incremental backup and bulk
 loading
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Tue, 09 Aug 2016 23:43:22 -0000


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

Devaraj Das commented on HBASE-14417:
-------------------------------------

The question is should we do this first or HBASE-14141 first. We need both in reality. We could put in a short term solution for backing up bulk-loaded data but wondering if we should bite the bullet and do HBASE-14141 and then this.

> Incremental backup and bulk loading
> -----------------------------------
>
>                 Key: HBASE-14417
>                 URL: https://issues.apache.org/jira/browse/HBASE-14417
>             Project: HBase
>          Issue Type: New Feature
>    Affects Versions: 2.0.0
>            Reporter: Vladimir Rodionov
>            Assignee: Vladimir Rodionov
>            Priority: Critical
>              Labels: backup
>             Fix For: 2.0.0
>
>
> Currently, incremental backup is based on WAL files. Bulk data loading bypasses WALs for obvious reasons, breaking incremental backups. The only way to continue backups after bulk loading is to create new full backup of a table. This may not be feasible for customers who do bulk loading regularly (say, every day).


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