[
https://issues.apache.org/jira/browse/HDFS-3395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13273430#comment-13273430
]
Daryn Sharp commented on HDFS-3395:
-----------------------------------
True, appending the port doesn't hurt anything. I was just adding an FYI
because it causes a fair amount of unnecessary work to process the host+port
tuple compared to passing each as an arg.
I looked all the places where the substitute method is used, so scratch my
comment about updating the config. I wonder though... Since a default of a
wildcard address is permissible if security is off, does this change introduce
inconsistent behavior when security is enabled? Kerberos requires a hostname,
so should it just sub in the resolved host name (ex.
{{NetUtils.getConnectAddres(addr).getHostName()}}) if the default is a wildcard
and security is enabled?
> 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
