Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-issues@hadoop.apache.org
Date: Tue, 17 May 2011 16:35:47 +0000 (UTC)
From: "Suresh Srinivas (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: 
 <1810373613.19628.1305650147696.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <935329242.10565.1305305567369.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (HDFS-1936) Updating the layout version from
 HDFS-1822 causes upgrade problems.
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Suresh Srinivas commented on HDFS-1936:
---------------------------------------

BTW I did not describe this earlier - I am removing the check for LV while consuming operations from editlog. Opcodes are suppose to be unique (at least that is the case right now) and there is no need to check for LV when the opcode was added.

This simplifies some of the conflict you might have been thinking about. Please look at the patch.


> Updating the layout version from HDFS-1822 causes upgrade problems.
> -------------------------------------------------------------------
>
>                 Key: HDFS-1936
>                 URL: https://issues.apache.org/jira/browse/HDFS-1936
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: name-node
>    Affects Versions: 0.22.0, 0.23.0
>            Reporter: Suresh Srinivas
>            Assignee: Suresh Srinivas
>            Priority: Blocker
>             Fix For: 0.22.0, 0.23.0
>
>         Attachments: HDFS-1936.22.patch, HDFS-1936.trunk.patch
>
>
> In HDFS-1822 and HDFS-1842, the layout versions for 203, 204, 22 and trunk were changed. Some of the namenode logic that depends on layout version is broken because of this. Read the comment for more description.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira