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:16:16 GMT

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

Konstantin Shvachko commented on HDFS-259:
------------------------------------------

> we can't upgrade from anything below 0.14 regardless.

we can, it just takes two steps instead of one. See the Release Note in HADOOP-2797.

We can safely remove the directory now. It should have been done in HADOOP-2797, but we missed
it at the time.

BTW, I know people who were recently running 0.15. Probably still do.


> 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.


Mime
View raw message