[
https://issues.apache.org/jira/browse/HADOOP-8372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13271482#comment-13271482
]
Kihwal Lee commented on HADOOP-8372:
------------------------------------
{noformat}
A host name (label) MUST NOT consist of all numeric values.
{noformat}
They are invalid host names, so the tests need to be fixed. I suggest you keep
the patch as is and fix the broken tests.
If a user puts an invalid host name in config, it will fail eventually. If this
method were to return the string as is in such cases, it would get "translated"
the same way somewhere down the road. We could add a full validation and make
it blow up in this method, but I don't think the gain is worth the complexity
of the check.
> normalizeHostName() in NetUtils is not working properly in resolving a
> hostname start with numeric character
> ------------------------------------------------------------------------------------------------------------
>
> Key: HADOOP-8372
> URL: https://issues.apache.org/jira/browse/HADOOP-8372
> Project: Hadoop Common
> Issue Type: Bug
> Components: io, util
> Affects Versions: 1.0.0, 0.23.0
> Reporter: Junping Du
> Assignee: Junping Du
> Attachments: HADOOP-8372.patch
>
>
> A valid host name can start with numeric value (You can refer RFC952, RFC1123
> or http://www.zytrax.com/books/dns/apa/names.html), so it is possible in a
> production environment, user name their hadoop nodes as: 1hosta, 2hostb, etc.
> But normalizeHostName() will recognise this hostname as IP address and return
> directly rather than resolving the real IP address. These nodes will be
> failed to get correct network topology if topology script/TableMapping only
> contains their IPs (without hostname).
--
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
