hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Allen Wittenauer (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-1822) Editlog opcodes overlap between 20 security and later releases
Date Tue, 12 Apr 2011 00:41:06 GMT

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

Allen Wittenauer commented on HDFS-1822:

Show me where the tarball is of Apache Hadoop 0.20-security because I don't see it on the
releases page ( http://hadoop.apache.org/common/releases.html ). Not there?  Doesn't that
make it as legit as Fred's Bargain Basement Distribution of Apache Hadoop?

bq. Suppose it is neither an incompatible change nor introducing other bad behaviors. Suppose
also the original patch was submitted to Apache Hadoop. We should accept it.

bq. On the other hand, if a patch is fixing a private distribution, we should not accept it.

But here's the problem:  this patch and my example cover both of these cases.  This patch
is not incompatible with any Apache release, but it does fix problems in private distributions.
So now what?

Let's assume that 0.20.203/204 makes it out the door (and, for the record, that branch has
a lot more problems than just this issue...).  What happens if someone upgrades from 0.20.203
to 0.21? (Trust me, people will.)

Side question for someone more skilled than I: Could someone generate a JIRA list that tracks
the changes in the opcodes?  I think they would be useful to look at, especially since it
has been alleged that the merge was 'bad'.  What made the merge go wonky?

> 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

View raw message