[
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
New patch attached.
- I changed the error message to: "Cannot rollback to storage version N using
this version of the NameNode, which uses storage version M. Please use the
previous version of HDFS to perform the rollback."
I think this wording is clearer, since users don't know the correspondance of
storage versions to Hadoop versions. The phrase "NameNode version -18" would
confuse them.
- Removed the accidental import
- Added a Preconditions check that storage.getLayoutVersion() ==
FSConstants.LAYOUT_VERSION when we save the image.
> 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
