hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "dhruba borthakur (JIRA)" <j...@apache.org>
Subject [jira] Updated: (HADOOP-5891) If dfs.http.address is default, SecondaryNameNode can't find NameNode
Date Tue, 02 Jun 2009 06:06:07 GMT

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

dhruba borthakur updated HADOOP-5891:

       Resolution: Fixed
    Fix Version/s: 0.21.0
           Status: Resolved  (was: Patch Available)

I just committed this. Thanks Todd!

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

View raw message