Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-issues@hadoop.apache.org
Message-ID: <6816858.158771290026474898.JavaMail.jira@thor>
Date: Wed, 17 Nov 2010 15:41:14 -0500 (EST)
From: "Eli Collins (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Subject: [jira] Updated: (HDFS-259) Remove intentionally corrupt 0.13
 directory layout creation
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/HDFS-259?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Eli Collins updated HDFS-259:
-----------------------------

      Resolution: Fixed
    Hadoop Flags: [Reviewed]
          Status: Resolved  (was: Patch Available)

I've committed this. Thanks Todd!

> 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
>             Fix For: 0.22.0
>
>         Attachments: hdfs-259.txt, hdfs-259.txt, hdfs-259.txt, hdfs-259.txt, hdfs-259.txt, 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.