You are viewing a plain text version of this content. The canonical link for it is here.

Posted to hdfs-issues@hadoop.apache.org by "Todd Lipcon (JIRA)" <ji...@apache.org> on 2011/05/12 00:07:47 UTC

[jira] [Commented] (HDFS-1919) Upgrade to federated namespace fails

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

Todd Lipcon commented on HDFS-1919:
-----------------------------------

I patched too soon... this allows the upgrade and initial startup. But, then, on next start, the NN fails with:

org.apache.hadoop.hdfs.server.common.InconsistentFSStateException: Directory /tmp/name1 is in an inconsistent state: file VERSION has no block pool 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: Todd Lipcon
>            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