hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Allen Wittenauer (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-5055) nn->2nn ignores dfs.namenode.secondary.http-address
Date Thu, 01 Aug 2013 12:25:49 GMT

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

Allen Wittenauer commented on HDFS-5055:

As demonstrated by the netstat output above but also by the log output below, 2NN is bringing
up the web interface on the correct hostname:port pair:

13/08/01 12:20:47 INFO namenode.SecondaryNameNode: Secondary Web-server up at: eat1-fiasconn02.grid.linkedin.com:50090

> nn->2nn ignores dfs.namenode.secondary.http-address
> ---------------------------------------------------
>                 Key: HDFS-5055
>                 URL: https://issues.apache.org/jira/browse/HDFS-5055
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: namenode
>    Affects Versions: 2.1.0-beta
>            Reporter: Allen Wittenauer
>            Priority: Blocker
> The primary namenode attempts to connect back to (incoming hostname):port regardless
of how dfs.namenode.secondary.http-address is configured.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

View raw message