[
https://issues.apache.org/jira/browse/HDFS-1919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Todd Lipcon reassigned HDFS-1919:
---------------------------------
Assignee: Suresh Srinivas (was: Todd Lipcon)
Hi Suresh. I'm reassigning this to you.
Unfortunately I don't have the log handy anymore, but you can easily reproduce
by formatting the NN with 0.22, then running hadoop namenode -upgrade with
trunk. It will start OK, but if you ^C and start again, it will fail with
missing blockpool ID.
> Upgrade to federated namespace fails
> ------------------------------------
>
> Key: HDFS-1919
> URL: https://issues.apache.org/jira/browse/HDFS-1919
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: name-node
> Affects Versions: 0.23.0
> Reporter: Todd Lipcon
> Assignee: Suresh Srinivas
> Priority: Blocker
> Fix For: 0.23.0
>
> Attachments: hdfs-1919.txt
>
>
> I formatted a namenode running off 0.22 branch, and trying to start it on
> trunk yields:
> org.apache.hadoop.hdfs.server.common.InconsistentFSStateException: Directory
> /tmp/name1 is in an inconsistent state: file VERSION has clusterID mising.
> It looks like 0.22 has LAYOUT_VERSION -33, but trunk has
> LAST_PRE_FEDERATION_LAYOUT_VERSION = -30, which is incorrect.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
