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-1936) Updating the layout version from HDFS-1822 causes upgrade problems.
Date Tue, 31 May 2011 18:44:47 GMT

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

Todd Lipcon commented on HDFS-1936:
-----------------------------------

Hi Suresh. I know it's been a singleton for a while, but with federation, it seems to cause
a lot more problems -- this test didn't ever time out before. So, I think the singleton issue
is a blocker, not just code cleanup, right?

I think the null checks you had to add are also due to this singleton usage -- they're masking
an issue but don't inherently make sense.

> Updating the layout version from HDFS-1822 causes upgrade problems.
> -------------------------------------------------------------------
>
>                 Key: HDFS-1936
>                 URL: https://issues.apache.org/jira/browse/HDFS-1936
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: name-node
>    Affects Versions: 0.22.0, 0.23.0
>            Reporter: Suresh Srinivas
>            Assignee: Suresh Srinivas
>            Priority: Blocker
>             Fix For: 0.22.0, 0.23.0
>
>         Attachments: HDFS-1936.3.patch, HDFS-1936.4.patch, HDFS-1936.6.patch, HDFS-1936.6.patch,
HDFS-1936.7.patch, HDFS-1936.8.patch, HDFS-1936.trunk.patch, hadoop-22-dfs-dir.tgz, hdfs-1936-with-testcase.txt
>
>
> In HDFS-1822 and HDFS-1842, the layout versions for 203, 204, 22 and trunk were changed.
Some of the namenode logic that depends on layout version is broken because of this. Read
the comment for more description.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message