hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ted Yu (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-14417) Incremental backup and bulk loading
Date Wed, 31 Aug 2016 15:25:22 GMT

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

Ted Yu commented on HBASE-14417:
--------------------------------

ReplicationHFileCleaner retrieves hfile refs from zookeeper in order to check for deletable
files.
The new BackupHFileCleaner would retrieve hfile refs by scanning hbase:backup table.
The hfile refs may be stored separately if no incremental / full backup has been performed
since the bulk load or, in manifest of some incremental backup.
Since we don't know which incremental backup manifest may contain related hfile ref, we need
to scan backwards until one incremental backup is found or, one full backup is found.

> 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)

Mime
View raw message