hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Todd Lipcon (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HDFS-1969) Running rollback on new-version namenode destroys namespace
Date Fri, 03 Jun 2011 22:07:47 GMT

     [ https://issues.apache.org/jira/browse/HDFS-1969?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Todd Lipcon updated HDFS-1969:

    Attachment: hdfs-1969.txt

Updated patch based on Eli's comments. I decided to use IllegalStateException since it describes
what's going on more clearly than AssertionError here.

I also took advantage of Suresh's new improvement which adds nice enums for LayoutVersion
checks, and updated the comments in that area of the code.

> 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

View raw message