You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-issues@hadoop.apache.org by "Eli Collins (Commented) (JIRA)" <ji...@apache.org> on 2011/12/08 23:45:40 UTC
[jira] [Commented] (HDFS-1842) Cannot upgrade 0.20.203 to 0.21 with
an editslog present
[ https://issues.apache.org/jira/browse/HDFS-1842?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13165652#comment-13165652 ]
Eli Collins commented on HDFS-1842:
-----------------------------------
Suresh,
Why did this change need to changes opcodes and LAYOUT_VERSION? This means a DFS upgrade is required in the stable series (203 -> 204), however trunk/23 can upgrade w/o this change - they just require users first squash the edits log with a saveNamespace, and this is only necessary when security is enabled. Was the idea that it's better to do two upgrades (203 -> 204 -> 23) instead of one upgrade (203/204 -> 23) that requires squashing the edits log when security is enabled?
Thanks,
Eli
> 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
> Assignee: Suresh Srinivas
> Priority: Blocker
> Attachments: HDFS-1842.rel203.patch, HDFS-1842.rel204.2.patch, HDFS-1842.rel204.3.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.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira