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

Hudson commented on HDFS-1969:
------------------------------

Integrated in Hadoop-Hdfs-trunk #689 (See 
[https://builds.apache.org/hudson/job/Hadoop-Hdfs-trunk/689/])
    HDFS-1969. Running rollback on new-version namenode destroys the namespace. 
Contributed by Todd Lipcon.

todd : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1132525
Files : 
* 
/hadoop/hdfs/trunk/src/java/org/apache/hadoop/hdfs/server/namenode/NNStorage.java
* /hadoop/hdfs/trunk/src/java/org/apache/hadoop/hdfs/server/common/Storage.java
* /hadoop/hdfs/trunk/src/test/hdfs/org/apache/hadoop/hdfs/TestDFSRollback.java
* 
/hadoop/hdfs/trunk/src/java/org/apache/hadoop/hdfs/server/namenode/FSImage.java
* /hadoop/hdfs/trunk/CHANGES.txt


> Running rollback on new-version namenode destroys namespace
> -----------------------------------------------------------
>
>                 Key: HDFS-1969
>                 URL: https://issues.apache.org/jira/browse/HDFS-1969
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: name-node
>    Affects Versions: 0.22.0
>            Reporter: Todd Lipcon
>            Assignee: Todd Lipcon
>            Priority: Blocker
>             Fix For: 0.22.0
>
>         Attachments: hdfs-1969.txt, hdfs-1969.txt, hdfs-1969.txt
>
>
> The following sequence leaves the namespace in an inconsistent/broken state:
> - format NN using 0.20 (or any prior release, probably)
> - run hdfs namenode -upgrade on 0.22. ^C the NN once it comes up.
> - run hdfs namenode -rollback on 0.22  (this should fail but doesn't!)
> This leaves the name directory in a state such that the version file claims 
> it's an 0.20 namespace, but the fsimage is in 0.22 format. It then crashes 
> when trying to start up.

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

Reply via email to