You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-dev@hadoop.apache.org by "Lorenzo Thione (JIRA)" <ji...@apache.org> on 2006/09/01 09:29:23 UTC
[jira] Commented: (HADOOP-497) DataNodes and TaskTrackers should be
able to report hostnames and ips relative to customizable network
interfaces and nameservers
[ http://issues.apache.org/jira/browse/HADOOP-497?page=comments#action_12432081 ]
Lorenzo Thione commented on HADOOP-497:
---------------------------------------
Just setting sun.net.spi.nameservice.nameservers worked for direct lookup but not for reverse lookup, at least when I first looked at it. This new patch does the job without using an external library, just using JNDI directly to query the DNS server. The new class has a new name (DNS.java) , and a new location (net) . A new package.html file was created as well. Finally, now network interface and nameserver are independently configurable for datanodes and tasktrackers. The names of the new properties have been changed to
net.dns.datanode.interface
net.dns.tasktracker.interface
net.dns.datanode.nameserver
net.dns.tasktracker.nameserver
> DataNodes and TaskTrackers should be able to report hostnames and ips relative to customizable network interfaces and nameservers
> ---------------------------------------------------------------------------------------------------------------------------------
>
> Key: HADOOP-497
> URL: http://issues.apache.org/jira/browse/HADOOP-497
> Project: Hadoop
> Issue Type: New Feature
> Components: mapred, dfs, util
> Affects Versions: 0.6.0
> Reporter: Lorenzo Thione
> Priority: Minor
> Attachments: dnsjava-2.0.2.jar, net-dns.patch, nif-utils.patch
>
>
> This patch allows for network configuration parameters to be aded to the hadoop-site.xml file. These parameters specify a network interface name and an optional nameserver hostname which DataNodes and TaskTrackers consult to resolve their hostnames from the IP bound to the specified network interface.
> This is useful when machines that are part of different physical or logical network need to participate in hadoop clusters as client nodes. The hostname and IP reported by InetAddress.getLocalHost() are not necessarily the ones that will allow the JobTracker and NameNode to reach the clients, as well as not necessarily the ones through which the DFS clients can reach the DataNodes.
> The configuration parameters are
> - cluster.report.nif
> - cluster.report.ns
> nif: takes the name of a network interface, like en0, en1 (on macs), eth0, etc...
> ns: the host name of a DNS server to use when resolving the IP bound to the specified nif
> These parameters are set by default to the value "default" which will replicate the current behavior of reporting InetAddress.getLocalHost().getHostName() and getHostAddress()
> As part of the patch, a new library dnsjava was added along with its license information (BSD license). The list of affected files is:
> src
> org.apache.hadoop.dfs.DataNode
> org.apache.hadoop.mapred.taskTracker
> org.apache.hadoop.util.NetworkUtils
> conf
> hadoop-default.xml
> lib
> dnsjava-2.0.2.jar
> dnsjava-2.0.2.LICENSE.txt
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira