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 Tue, 06 Aug 2013 18:31:49 GMT

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

Allen Wittenauer commented on HDFS-5055:

Actually... why is the NN doing a reverse look up if we provided a value for dfs.namenode.secondary.http-address?
 Since the config is defined/clearly not wildcarded, it shouldn't be resorting to this behavior
(e.g., wildly unpredictable).  This is looking more and more like HDFS-3404 is bugged.
> 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