[
https://issues.apache.org/jira/browse/HADOOP-6397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12806204#action_12806204
]
Scott Chen commented on HADOOP-6397:
------------------------------------
Add the unit test and use the IP pattern to check if the name is already an IP.
@Christian: I am also changing our internal trunk for this part. So I have
modified the patch. I hope you don't mind.
> topology script called with host names instead of IP addresses
> --------------------------------------------------------------
>
> Key: HADOOP-6397
> URL: https://issues.apache.org/jira/browse/HADOOP-6397
> Project: Hadoop Common
> Issue Type: Bug
> Components: util
> Affects Versions: 0.20.1
> Reporter: Christian Kunz
> Attachments: HADOOP-6397-v2.patch, HADOOP-6397.patch
>
>
> According to the 'Hadoop Rack Awareness' section on
> http://hadoop.apache.org/common/docs/r0.20.0/cluster_setup.html the
> script/program topology.script.file.name can assume that names are passed in
> as IP addresses.
> This seems to work for hdfs, but the rack-awareness of the JobTracker does
> not always work, depending on the hostnames of the cluster, because of a bug
> in the method normalizeHostName of org.apache.hadoop.net.NetUtils.java:
> It returns the host name as-is when it decides that the string passed-in is
> already an IP but actually it checks whether the string starts with a valid
> hex character!
> There is no need to check at all, because InetAddress.getByName is smart
> enough to not do a dns lookup when the name is an IP address.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
