hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Todd Lipcon (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-4655) Document architecture of backups
Date Wed, 16 Nov 2011 20:59:51 GMT

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

Todd Lipcon commented on HBASE-4655:

Two quick notes from looking over the doc:

- the names are a little confusing to me - "in-cluster back up" is actually two clusters,
right? I'd call your "RBU" an in-cluster backup, I'd call your CBU an "in-datacenter backup",
and I'd call your DBU a "cross-datacenter backup", "DR backup", or "BCP backup".

- For RBU, maybe we can get atomicity in a simpler manner by having the region server initiate
the copy of hfiles? It can hold the lock to block flushes while the copies happen (they're
hard-link copies, right?) 

> Document architecture of backups
> --------------------------------
>                 Key: HBASE-4655
>                 URL: https://issues.apache.org/jira/browse/HBASE-4655
>             Project: HBase
>          Issue Type: Sub-task
>          Components: documentation, regionserver
>            Reporter: Karthik Ranganathan
>            Assignee: Karthik Ranganathan
>         Attachments: HBase Backups Architecture.docx
> Basic idea behind the backup architecture for HBase

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message