[
https://issues.apache.org/jira/browse/HDFS-5055?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13730196#comment-13730196
]
Aaron T. Myers commented on HDFS-5055:
--------------------------------------
Yep, this behavior did indeed change. The issue was exactly what was described
in HDFS-4304 - you couldn't set the 2NN HTTP address setting to the wildcard
address since if the NN were to use that it obviously couldn't connect to the
2NN unless the two processes were co-located on the same machine.
I think the best solution to this (and other) issues would be to switch to
using an HTTP PUT or POST for the 2NN to send the fsimage back to the NN,
instead of having the 2NN do a GET which in turn causes the NN to do another
GET back to the 2NN. That's what's proposed in this JIRA: HDFS-3405.
> 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
