hadoop-hdfs-issues mailing list archives

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

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

Todd Lipcon commented on HDFS-259:
----------------------------------

I looked through some of the old releases, here are the corresponding layout versions:

||version||LAYOUT_VERSION||
|0.12.0|-3|
|0.13.0|-4|
|0.14.0|-7|
|0.15.0|-10|
|0.16.0|-11|
|0.17.0|-13|
|0.18.0|-16|
|0.19.0|-18|

Currently LAST_UPGRADABLE_LAYOUT_VERSION is -7, corresponding to 0.14. LAST_PRE_UPGRADE_LAYOUT_VERSION
is -3. So, we can't upgrade from anything below 0.14 regardless. I don't know of anyone running
anything that old anymore (it's more than 3 years ago!) and I think we may as well drop these
crutches which were added by HADOOP-1242.

I think we can also get rid fo the isConversionNeeded() functions, etc, which deal with upgrade
from this kind of old version.

> 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
>            Reporter: Todd Lipcon
>
> 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.


Mime
View raw message