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] [Commented] (HDFS-1969) Running rollback on new-version namenode destroys namespace
Date Fri, 27 May 2011 21:03:47 GMT

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

Todd Lipcon commented on HDFS-1969:

Konst, would you mind +1ing this as is? If you want, we can file a JIRA for the overall improvement
of removing the support for saving past-layout VERSION files from the main source tree. But,
it looks moderately complex to do cleanly, and this patch as is fixes a blocker bug and doesn't
make the issue any worse than it already is.

> 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
> 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