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 21:18:06 +0000 (UTC)
From: "Allen Wittenauer (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: 
 <2040660019.56205.1302729486112.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=13019558#comment-13019558 ] 

Allen Wittenauer commented on HDFS-1822:
----------------------------------------

bq. the new software can handle the old edit logs since opcodes are private unstable APIs

You can't have it both ways.  If new software understands the old opcodes that essentially declares them stable.

bq. I believe my approach avoids opcode conversion in downstream releases.

Won't the editslog still need to get processed during an upgrade?

> 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