Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-issues@hadoop.apache.org
Date: Thu, 12 May 2011 06:37:47 +0000 (UTC)
From: "Suresh Srinivas (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: 
 <1652734281.6040.1305182267769.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1637480055.4984.1305151308071.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (HDFS-1919) Upgrade to federated namespace fails
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Suresh Srinivas commented on HDFS-1919:
---------------------------------------

I do not see any restarts failing. Perhaps you did not clean build and the static LV was not updated in some classes.

However, I do see that bumping up the layout version for 203, 22 and trunk (from HDFS-1842 and HDFS-1824) has caused problems with some of the version checks for new fsimage scheme of loading and checksum of edits etc. I will change the title of this bug and fix them.

> 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