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] [Comment Edited] (HBASE-14417) Incremental backup and bulk loading
Date Mon, 21 Nov 2016 23:33:58 GMT

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

Ted Yu edited comment on HBASE-14417 at 11/21/16 11:33 PM:
-----------------------------------------------------------

org.apache.hadoop.hbase.backup.BackupHFileCleaner should be registered through hbase.master.hfilecleaner.plugins
. It is responsible for keeping bulk loaded hfiles so that incremental backup can pick them
up.
org.apache.hadoop.hbase.backup.BackupObserver should be registered through hbase.coprocessor.region.classes
It is notified when bulk load completes and writes records into hbase:backup table.


was (Author: yuzhihong@gmail.com):
BackupHFileCleaner should be registered through hbase.master.hfilecleaner.plugins . It is
responsible for keeping bulk loaded hfiles so that incremental backup can pick them up.
BackupObserver should be registered through hbase.coprocessor.region.classes
It is notified when bulk load completes and writes records into hbase:backup table.

> 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: Ted Yu
>            Priority: Critical
>              Labels: backup
>             Fix For: 2.0.0
>
>         Attachments: 14417-tbl-ext.v9.txt, 14417.v1.txt, 14417.v11.txt, 14417.v13.txt,
14417.v2.txt, 14417.v21.txt, 14417.v23.txt, 14417.v24.txt, 14417.v25.txt, 14417.v6.txt
>
>
> 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).
> Google doc for design:
> https://docs.google.com/document/d/1ACCLsecHDvzVSasORgqqRNrloGx4mNYIbvAU7lq5lJE



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

Mime
View raw message