Mailing-List: contact core-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: core-dev@hadoop.apache.org
Message-ID: <119368369.1214419845648.JavaMail.jira@brutus>
Date: Wed, 25 Jun 2008 11:50:45 -0700 (PDT)
From: "dhruba borthakur (JIRA)" <jira@apache.org>
To: core-dev@hadoop.apache.org
Subject: [jira] Commented: (HADOOP-3637) Support for snapshots
In-Reply-To: <721591721.1214353544996.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/HADOOP-3637?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12608151#action_12608151 ] 

dhruba borthakur commented on HADOOP-3637:
------------------------------------------

Good question. I think a typical installation would have the namenode and secondary namenode in the same data center. So, in a disaster scenario, both of these machines might be unavailable. In short, a disaster recovery solution would need something more than the secondary namenode.

I think that the request fr Joydeep is to transfer the snapshot image into a remote location (possibly outside the data center) so that it can allow namenode recovery after a disaster. One assumption for this recovery is that at at least one replica of most hdfs blocks be not affected by the disaster.


> Support for snapshots
> ---------------------
>
>                 Key: HADOOP-3637
>                 URL: https://issues.apache.org/jira/browse/HADOOP-3637
>             Project: Hadoop Core
>          Issue Type: New Feature
>          Components: dfs
>            Reporter: dhruba borthakur
>            Assignee: dhruba borthakur
>
> Support HDFS snapshots. It should support creating snapshots without shutting down the file system. Snapshot creation should be lightweight and a typical system should be able to support a few thousands concurrent snapshots. There should be a way to surface (i.e. mount) a few of these snapshots simultaneously.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.