hbase-issues mailing list archives

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

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

stack commented on HBASE-4655:

Echo Todd #1 remarks.

For '...incremental backups at the Stage 1 (RBU) level', won't the time between step between
b and d be 'large' and during the copy time, the list of files could change on you; i.e. when
you go to copy a file, it maybe have been removed because it'd been compacted.  What do you
do in this case?  (Your list may not included the compacted file)?

For "a.The backups rely on the clocks across the various region-servers for determining the
point in time to which the edits are re-played", so, say a server is lagging the others by
a good bit?   When replaying the edits, you'd replay edits from when this lagging server said
the backup began?

How will you know which hlogs to replay?  You'll open it and look at first and last edits
in the file?  Or should we write out metadata files for hlogs?  Or is it enough relying on
hdfs modtime?

Looks great K.

> 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