Return-Path: Delivered-To: apmail-hadoop-hbase-issues-archive@minotaur.apache.org Received: (qmail 96587 invoked from network); 1 Apr 2010 20:54:50 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 1 Apr 2010 20:54:50 -0000 Received: (qmail 20809 invoked by uid 500); 1 Apr 2010 20:54:50 -0000 Delivered-To: apmail-hadoop-hbase-issues-archive@hadoop.apache.org Received: (qmail 20787 invoked by uid 500); 1 Apr 2010 20:54:50 -0000 Mailing-List: contact hbase-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list hbase-issues@hadoop.apache.org Received: (qmail 20779 invoked by uid 99); 1 Apr 2010 20:54:50 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 01 Apr 2010 20:54: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.140] (HELO brutus.apache.org) (140.211.11.140) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 01 Apr 2010 20:54:48 +0000 Received: from brutus.apache.org (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 1FBE3234C4B1 for ; Thu, 1 Apr 2010 20:54:27 +0000 (UTC) Message-ID: <48264325.642821270155267125.JavaMail.jira@brutus.apache.org> Date: Thu, 1 Apr 2010 20:54:27 +0000 (UTC) From: "stack (JIRA)" To: hbase-issues@hadoop.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=12852545#action_12852545 ] stack commented on HBASE-50: ---------------------------- .bq Why is it that you say we cannot flush and instead need to use the WAL? Just an overhead thing?... Yes. Want to keep snapshot window narrow. Don't want it spanning flush signal and wait on flush to complete. This has the gsoc label on it. Let me know if you want me to remove it because you fellas want to grab it. > Snapshot of table > ----------------- > > Key: HBASE-50 > URL: https://issues.apache.org/jira/browse/HBASE-50 > Project: Hadoop HBase > Issue Type: New Feature > Reporter: Billy Pearson > Priority: Minor > > 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.