You are viewing a plain text version of this content. The canonical link for it is here.

Posted to hdfs-dev@hadoop.apache.org by "Suresh Srinivas (JIRA)" <ji...@apache.org> on 2011/04/23 01:12:06 UTC

[jira] [Resolved] (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:all-tabpanel ]

Suresh Srinivas resolved HDFS-1842.
-----------------------------------

      Resolution: Fixed
    Release Note: I committed the patch. Konstantin, I wanted to commit this patch, as soon as possible. Please do review and let me know your feedback. I will open another jira to take care of the comments, if there are any.
    Hadoop Flags: [Reviewed]

> 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.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.
For more information on JIRA, see: http://www.atlassian.com/software/jira