[
https://issues.apache.org/jira/browse/HADOOP-8372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13271356#comment-13271356
]
Junping Du commented on HADOOP-8372:
------------------------------------
This patch will use InetAddress.getByName(String) to judge if a string is a
numeric IP address or symbolic address(hostname). However, this JAVA api will
also take trouble that it will translate some numeric hostname like: 1.2.3 to
1.2.0.3 (or 1.2 to 1.0.0.2) as it assume this patent of numeric string is IP
address. It will break some current hadoop tests with "1.2.3" as hostname (like
in TestTableMapping). Thoughts?
> 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
