[
https://issues.apache.org/jira/browse/HDFS-1842?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13022365#comment-13022365
]
Konstantin Shvachko commented on HDFS-1842:
-------------------------------------------
Yes rollback is not needed as image and edits loading does not change any files
or directories.
Both choices work work me.
(1) provides faster failure. Only the size of the empty edits is sizeof(long),
which is the layoutVersion size.
(2) is also fine and would be my preference. Informed admins will do
saveNamespace() before upgrading, so the edits will be empty. But if they
forget the upgrade will fail after 10 minutes, which is o(the time to restart
the name-node with 203 and then again upgrade).
> 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.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
