[
https://issues.apache.org/jira/browse/HDFS-1464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13032095#comment-13032095
]
Eli Collins commented on HDFS-1464:
-----------------------------------
Hey Jakob,
Would a patch that makes the 2NN not start with 0.0.0.0 if security is on be
acceptable to you?
Thanks,
Eli
> Fix reporting of 2NN address when dfs.secondary.http.address is default
> (wildcard)
> ----------------------------------------------------------------------------------
>
> Key: HDFS-1464
> URL: https://issues.apache.org/jira/browse/HDFS-1464
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: name-node
> Affects Versions: 0.22.0
> Reporter: Todd Lipcon
> Assignee: Todd Lipcon
> Attachments: hdfs-1464.txt
>
>
> HDFS-1080 broke the way that the 2NN identifies its own hostname to the NN
> during checkpoint upload. It used to use the local hostname, which as
> HDFS-1080 pointed out was error prone if it had multiple interfaces, etc. But
> now, with the default setting of dfs.secondary.http.address, the 2NN reports
> "0.0.0.0", which won't work either.
> We should look for the wildcard bind address and use the local hostname in
> that case, like we used to.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
