[
https://issues.apache.org/jira/browse/HDFS-1842?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13021926#comment-13021926
]
Konstantin Shvachko commented on HDFS-1842:
-------------------------------------------
Saw your comment in HDFS-1822. The plan looks good to me.
Talked to Jakob. He had an idea of saving namespace before upgrading. You
mention it in HDFS-1822 too.
This can make your 204 patch simpler. You don't need to convert codes, while
reading the edits. You just need to demand that the edits is empty. Which will
require either saving namespace before exiting the NN.0.203, or restarting it
one last time before upgrading.
I think this will make things even better.
> 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
