[
https://issues.apache.org/jira/browse/HDFS-1842?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Suresh Srinivas updated HDFS-1842:
----------------------------------
Attachment: HDFS-1842.rel204.1.patch
New patch for release 204. I made an additional modification from the previous
proposal:
Instead of checking for number edits and then printing an error for 203 release
to say editlog must be empty, I print the error only when editlog could not be
loaded on 203 release.
Given that opcode in conflict are security related, non-secure deployments will
not have any problem to load 203 edits in 204. In such a case, editlog can be
loaded without needing restart. Only on secure deployments, an error will be
thrown for restarting namenode.
> Cannot upgrade 0.20.203 to 0.21 with an editslog present
> --------------------------------------------------------
>
> Key: HDFS-1842
> URL: https://issues.apache.org/jira/browse/HDFS-1842
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Components: name-node
> Affects Versions: 0.20.203.0
> Reporter: Allen Wittenauer
> Priority: Blocker
> Attachments: HDFS-1842.rel203.patch, HDFS-1842.rel204.1.patch,
> HDFS-1842.rel204.patch
>
>
> If a user installs 0.20.203 and then upgrades to 0.21 with an editslog
> present, 0.21 will corrupt the file system due to opcode re-usage.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
