[
https://issues.apache.org/jira/browse/HDFS-3395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13273368#comment-13273368
]
Aaron T. Myers commented on HDFS-3395:
--------------------------------------
bq. This really should have used NetUtils.createSocketAddrForHost(host, port)
instead of string appending the port.
Good point, though this particular use of it is pretty innocuous, as the patch
is just using a dummy port value (0) so we can get an InetSocketAddress on
which we can call isAnyLocalAddress().
bq. Also, would it work correctly if the config was updated with the connect
address for the socket? There's a Configuration#updateConnectAddr(key, addr)
that will do that.
I'm not sure I understand this. What config are you referring to updating?
> NN doesn't start with HA+security enabled and HTTP address set to 0.0.0.0
> -------------------------------------------------------------------------
>
> Key: HDFS-3395
> URL: https://issues.apache.org/jira/browse/HDFS-3395
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: name-node
> Affects Versions: 2.0.0
> Reporter: Aaron T. Myers
> Assignee: Aaron T. Myers
> Fix For: 2.0.0
>
> Attachments: HDFS-3395.patch
>
>
> DFSUtil#substituteForWildcardAddress subs in a default hostname if the given
> hostname is 0.0.0.0. However, this function throws an exception if the given
> hostname is set to 0.0.0.0 and security is enabled, regardless of whether the
> default hostname is also 0.0.0.0. This function shouldn't throw an exception
> unless both addresses are set to 0.0.0.0.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
