hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Konstantin Shvachko (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HDFS-259) Remove intentionally corrupt 0.13 directory layout creation
Date Thu, 21 Oct 2010 05:32:17 GMT

    [ https://issues.apache.org/jira/browse/HDFS-259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12923328#action_12923328

Konstantin Shvachko commented on HDFS-259:

> This patch simply removes the code that creates this directory and looks for it. 

Not so easy. You should guarantee that it throws an exception, when somebody tries to upgrade
from a very old version. The exception should explain what steps are required to get to current
version. That is why I think removing isConversionNeeded() is a mistake.
Let me know if you need old images for testing. I keep those handy just in case.

> Remove intentionally corrupt 0.13 directory layout creation
> -----------------------------------------------------------
>                 Key: HDFS-259
>                 URL: https://issues.apache.org/jira/browse/HDFS-259
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>    Affects Versions: 0.22.0
>            Reporter: Todd Lipcon
>            Assignee: Todd Lipcon
>         Attachments: hdfs-259.txt
> Given that 0.13 is incredibly old at this point, I think the likelihood of anyone trying
to start an 0.20+ namenode on an 0.13 directly layout is essentially nil. The intentionally-corrupt
"${dfs.name.dir}/image/" directory just serves to confuse new users at this point, so I propose
removing it.
> If no one objects, I'll submit a patch. If there are objections, I propose at least adding
a README explaining its purpose (same text as in the corrupt fsimage file)

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message