Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-issues@hadoop.apache.org
Date: Wed, 14 Mar 2012 23:48:41 +0000 (UTC)
From: "Eli Collins (Commented) (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: 
 <255352055.16627.1331768921496.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1367329781.728.1331504320153.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (HDFS-3075) Backport HADOOP-4885 to branch-1
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/HDFS-3075?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13229767#comment-13229767 ] 

Eli Collins commented on HDFS-3075:
-----------------------------------

Sorry, posted to the wrong jira!
                
> Backport HADOOP-4885 to branch-1
> --------------------------------
>
>                 Key: HDFS-3075
>                 URL: https://issues.apache.org/jira/browse/HDFS-3075
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>          Components: name-node
>            Reporter: Brandon Li
>            Assignee: Brandon Li
>             Fix For: 1.1.0
>
>
> When a storage directory is inaccessible, namenode removes it from the valid storage dir list to a removedStorageDirs list. Those storage directories will not be restored when they become healthy again. 
> The proposed solution is to restore the previous failed directories at the beginning of checkpointing, say, rollEdits, by copying necessary metadata files from healthy directory to unhealthy ones. In this way, whenever a failed storage directory is recovered by the administrator, he/she can immediately force a checkpointing to restored a failed directory.
> See also HADOOP-4885.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira