[
https://issues.apache.org/jira/browse/HBASE-50?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12897246#action_12897246
]
HBase Review Board commented on HBASE-50:
-----------------------------------------
Message from: "Chongxin Li" <[email protected]>
bq. On 2010-08-10 22:40:31, Ted Yu wrote:
bq. > src/main/java/org/apache/hadoop/hbase/master/HMaster.java, line 962
bq. > <http://review.cloudera.org/r/467/diff/3/?file=6015#file6015line962>
bq. >
bq. > Moving crashed snapshots has two benefits:
bq. > 1. future call to listSnapshots() wouldn't encounter IOException.
bq. > 2. it's easy for user to get statistics on failed snapshots and
analyze them
bq. >
bq. > Or, if you log enough information when cleaning up the failed
snapshot.
bq. >
What about snapshot fails when it is being created? Currently it is cleaned up
if exception occurs in HMaster.snapshot. Should we also move it to this
directory? Then for reference information sync, should we also take the
reference files of these failed snapshots into account?
- Chongxin
-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
http://review.cloudera.org/r/467/#review830
-----------------------------------------------------------
> Snapshot of table
> -----------------
>
> Key: HBASE-50
> URL: https://issues.apache.org/jira/browse/HBASE-50
> Project: HBase
> Issue Type: New Feature
> Reporter: Billy Pearson
> Assignee: Li Chongxin
> Priority: Minor
> Attachments: HBase Snapshot Design Report V2.pdf, HBase Snapshot
> Design Report V3.pdf, HBase Snapshot Implementation Plan.pdf, Snapshot Class
> Diagram.png
>
>
> Havening an option to take a snapshot of a table would be vary useful in
> production.
> What I would like to see this option do is do a merge of all the data into
> one or more files stored in the same folder on the dfs. This way we could
> save data in case of a software bug in hadoop or user code.
> The other advantage would be to be able to export a table to multi locations.
> Say I had a read_only table that must be online. I could take a snapshot of
> it when needed and export it to a separate data center and have it loaded
> there and then i would have it online at multi data centers for load
> balancing and failover.
> I understand that hadoop takes the need out of havening backup to protect
> from failed servers, but this does not protect use from software bugs that
> might delete or alter data in ways we did not plan. We should have a way we
> can roll back a dataset.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
