[
https://issues.apache.org/jira/browse/HDFS-1822?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13021701#comment-13021701
]
Suresh Srinivas commented on HDFS-1822:
---------------------------------------
It took me some time to recover and get back to this jira :-). I like
Konstantin's proposal. Here is some changes and additional clarification:
203 and releases before that have opcode conflicts. Along similar lines as
konstantin, I propose:
# Currently the LV of trunk is -30. Change layout versions as follows:
#* 203 to -31
#* 204 to -32
#* 21 will remain -24.
#* 22 to -33
#* Reserve all these layout versions in trunk FSConstants.java and bump trunk
LV to -34.
#* In 204 add code to handle opcode conflicts. This code will remain in 2xx
release only.
# Add code in 22 and trunk to throw an error if upgrade is from 203 or older
2xx releases and editlog is not empty, to say "must upgrade to 204 or must save
namespace before upgrade." release first.
# With this the upgrades will work as follows:
#* 203 and later 2xx releases -> 21 fails, since we do not support this upgrade
path.
#* 203 -> 22, 23 will fail with an error indicating must upgrade to 204 first,
if edit logs are not empty.
#* 204 -> 22, 23 will work.
#* 21 -> 22, 23 and 22 -> 23 will work.
# Disallow 21 to 203 upgrade by checking for LV version -24 with an error
"Upgrade not supported".
> 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
