Return-Path: X-Original-To: apmail-hadoop-hdfs-issues-archive@minotaur.apache.org Delivered-To: apmail-hadoop-hdfs-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 97346D5EF for ; Mon, 22 Oct 2012 19:02:16 +0000 (UTC) Received: (qmail 24254 invoked by uid 500); 22 Oct 2012 19:02:16 -0000 Delivered-To: apmail-hadoop-hdfs-issues-archive@hadoop.apache.org Received: (qmail 24220 invoked by uid 500); 22 Oct 2012 19:02:16 -0000 Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: hdfs-issues@hadoop.apache.org Delivered-To: mailing list hdfs-issues@hadoop.apache.org Received: (qmail 24205 invoked by uid 99); 22 Oct 2012 19:02:16 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 22 Oct 2012 19:02:16 +0000 Date: Mon, 22 Oct 2012 19:02:16 +0000 (UTC) From: "Tsz Wo (Nicholas), SZE (JIRA)" To: hdfs-issues@hadoop.apache.org Message-ID: <1030705172.11465.1350932536371.JavaMail.jiratomcat@arcas> In-Reply-To: <600033870.49553.1326826119648.JavaMail.tomcat@hel.zones.apache.org> Subject: [jira] [Commented] (HDFS-2802) Support for RW/RO snapshots in HDFS MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/HDFS-2802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13481643#comment-13481643 ] Tsz Wo (Nicholas), SZE commented on HDFS-2802: ---------------------------------------------- O(1) memory usage in general does not not seem possible since the original files/directories could be modified. So the best case is O(N) memory usage in general. However, it is possible to have O(1) memory usage at snapshot creation. For small subtrees, i.e. when N is small, it does not matter if it is O(1) or O(N). Such snapshot feature already benefits many applications. So we are going to implement O(N) snapshot creation in the first phase and then optimization it later. Then, we could have the snapshot feature out early instead of spending a long time to come up a complicated design and implementation. A complicated design also increases the risk of bugs in the implementation. > Support for RW/RO snapshots in HDFS > ----------------------------------- > > Key: HDFS-2802 > URL: https://issues.apache.org/jira/browse/HDFS-2802 > Project: Hadoop HDFS > Issue Type: New Feature > Components: data-node, name-node > Reporter: Hari Mankude > Assignee: Hari Mankude > Attachments: snap.patch, snapshot-one-pager.pdf, Snapshots20121018.pdf > > > Snapshots are point in time images of parts of the filesystem or the entire filesystem. Snapshots can be a read-only or a read-write point in time copy of the filesystem. There are several use cases for snapshots in HDFS. I will post a detailed write-up soon with with more information. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira