hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "gary murry (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-5891) If dfs.http.address is default, SecondaryNameNode can't find NameNode
Date Wed, 03 Jun 2009 16:24:07 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-5891?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12715972#action_12715972
] 

gary murry commented on HADOOP-5891:
------------------------------------

>From Email exchange: This code change is already exercised by TestCheckpoint.

> If dfs.http.address is default, SecondaryNameNode can't find NameNode
> ---------------------------------------------------------------------
>
>                 Key: HADOOP-5891
>                 URL: https://issues.apache.org/jira/browse/HADOOP-5891
>             Project: Hadoop Core
>          Issue Type: Bug
>          Components: dfs
>            Reporter: Todd Lipcon
>            Assignee: Todd Lipcon
>             Fix For: 0.21.0
>
>         Attachments: hadoop-5891.txt
>
>
> As detailed in this blog post:
> http://www.cloudera.com/blog/2009/02/10/multi-host-secondarynamenode-configuration/
> if dfs.http.address is not configured, and the 2NN is a different machine from the NN,
the 2NN fails to connect.
> In SecondaryNameNode.getInfoServer, the 2NN should notice a "0.0.0.0" dfs.http.address
and, in that case, pull the hostname out of fs.default.name. This would fix the default configuration
to work properly for most users.

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