[
https://issues.apache.org/jira/browse/HDFS-5055?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13731123#comment-13731123
]
Suresh Srinivas commented on HDFS-5055:
---------------------------------------
bq. Since the config is defined/clearly not wildcarded, it shouldn't be
resorting to this behavior (e.g., wildly unpredictable).
+1. I was thinking along the same lines.
Given that this is a blocker, we need to fix this ASAP. [~atm] do you have
bandwidth to fix this? Alternatively we can revert this change and add it back
in another dot release?
> 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
