Return-Path: Delivered-To: apmail-hbase-issues-archive@www.apache.org Received: (qmail 93896 invoked from network); 9 Jun 2010 13:56:50 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 9 Jun 2010 13:56:50 -0000 Received: (qmail 53403 invoked by uid 500); 9 Jun 2010 13:56:50 -0000 Delivered-To: apmail-hbase-issues-archive@hbase.apache.org Received: (qmail 53289 invoked by uid 500); 9 Jun 2010 13:56:50 -0000 Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list issues@hbase.apache.org Received: (qmail 53281 invoked by uid 99); 9 Jun 2010 13:56:50 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 09 Jun 2010 13:56:50 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.22] (HELO thor.apache.org) (140.211.11.22) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 09 Jun 2010 13:56:47 +0000 Received: from thor (localhost [127.0.0.1]) by thor.apache.org (8.13.8+Sun/8.13.8) with ESMTP id o59DuPn1015894 for ; Wed, 9 Jun 2010 13:56:26 GMT Message-ID: <31629856.2361276091785896.JavaMail.jira@thor> Date: Wed, 9 Jun 2010 09:56:25 -0400 (EDT) From: "Li Chongxin (JIRA)" To: issues@hbase.apache.org Subject: [jira] Commented: (HBASE-50) Snapshot of table MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/HBASE-50?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12877076#action_12877076 ] Li Chongxin commented on HBASE-50: ---------------------------------- @ J-D Yes..That sounds good. I will implement another LogCleanerDelegate, say ReferenceLogCleaner or SnapshotLogCleaner. Do you archive any other files besides log files, say HFiles? > 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, snapshot-src.zip > > > 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.