[
https://issues.apache.org/jira/browse/HDFS-5055?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13730184#comment-13730184
]
Suresh Srinivas commented on HDFS-5055:
---------------------------------------
This part has changed quite a bit! Spent couple of hours digging this.
In branch-1, the secondary namenode passes the host name to connect to get the
image in the http param "machine".
This is no longer passed from the secondary. This change was done in HDFS-3404.
Now the remote address is inferred based on the remote host. Here is the
snippet of code where this is done:
{code}
machineName = request.getRemoteHost();
if (InetAddresses.isInetAddress(machineName)) {
machineName = NetUtils.getHostNameOfIP(machineName);
}
{code}
[~aw], this could that be causing the issue in your setup.
[~atm], can you take a look at this issue?
> 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
