hbase-issues mailing list archives

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

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

Karthik Ranganathan commented on HBASE-4655:
--------------------------------------------

For #1, totally :) internally, we use the term "cluster" to denote a section of the data center
(as opposed to the HBase cluster), a data center is composed of a number of "clusters", hence
the name. in-DC and cross-DC work.

For #2, this makes the running cluster stall and not take updates for the time period of the
copy. It is fast-copy with hard-links underneath, but there is nothing in the current design
that would stop it from being used against a remote cluster or a DFS version without the hard-link.
Also, if for some reason the hard link fails, it does a deep copy, so it could have longer
stalls.
                
> 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

        

Mime
View raw message