You are viewing a plain text version of this content. The canonical link for it is here.

Posted to hdfs-issues@hadoop.apache.org by "Boris Shkolnik (JIRA)" <ji...@apache.org> on 2011/02/03 19:28:29 UTC

[jira] Commented: (HDFS-1602) Fix HADOOP-4885 for it is doesn't work as expected.

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

Boris Shkolnik commented on HDFS-1602:
--------------------------------------

I've looked at testStorageRestore failure. Seems like the problem is that when we are trying to restore a storage dir, we format it , which always saves the current in-memory state into a new fsimage. So instead we should restore a storage without storing creating new fsimage. It will be copied from the CheckPoint.
Here is a patch for trunk to do it. Please review.

> Fix HADOOP-4885 for it is doesn't work as expected.
> ---------------------------------------------------
>
>                 Key: HDFS-1602
>                 URL: https://issues.apache.org/jira/browse/HDFS-1602
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: name-node
>    Affects Versions: 0.21.0
>            Reporter: Konstantin Boudnik
>
> NameNode storage restore functionality doesn't work (as HDFS-903 demonstrated). This needs to be either disabled, or removed, or fixed. This feature also fails HDFS-1496

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira