Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-issues@hadoop.apache.org
Date: Wed, 13 Apr 2011 18:34:05 +0000 (UTC)
From: "Konstantin Shvachko (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: 
 <1585013477.55724.1302719645789.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1154777554.44805.1302292745765.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (HDFS-1822) Editlog opcodes overlap between 20
 security and later releases
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Konstantin Shvachko commented on HDFS-1822:
-------------------------------------------

Proposed change seems odd. I understand there was a mistake made while introducing these ops to 0.20s. So correcting this mistake by introducing a work around into 0.22 and using it forever is bad. 
I did not exactly understood what was vetoed.

I think a nicer way to handle this is this.
Let's upgrade all four branches at once.
h-0.20.s    LV -19 -> -29
h-0.21      LV -27 -> -30
h-0.22      LV -28 -> -31
h-0.23      LV -27 -> -32

h-0.20.s  with  LV -29 will provide conversion from the -19 ops to the right ones.
LV -19 should be banned for h-0.21,22,23

Will that work?

> Editlog opcodes overlap between 20 security and later releases
> --------------------------------------------------------------
>
>                 Key: HDFS-1822
>                 URL: https://issues.apache.org/jira/browse/HDFS-1822
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: name-node
>    Affects Versions: 0.21.0, 0.22.0, 0.23.0
>            Reporter: Suresh Srinivas
>            Assignee: Suresh Srinivas
>            Priority: Blocker
>             Fix For: 0.22.0, 0.23.0
>
>         Attachments: HDFS-1822.patch
>
>
> Same opcode are used for different operations between 0.20.security, 0.22 and 0.23. This results in failure to load editlogs on later release, especially during upgrades.

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