hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Konstantin Shvachko (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-1822) Editlog opcodes overlap between 20 security and later releases
Date Wed, 13 Apr 2011 21:50:05 GMT

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

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

I propose to first upgrade h-0.20s from -19 to -29. This will convert opcodes to the right
ones for h-0.20s. Then you can upgrade it to h-0.21,22,23, which will have higher LV -30,-31,-32
respectively  (according to the table above).
h-0.21,22,23 will also prohibit to upgrade from -19, asking to upgrade to -29 first.
But there is no confusing opcode conversions in releases h-0.21,22,23 and in the future. This
will all be buried and forgotten in h-0.20s.

> 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

Mime
View raw message