hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Doug Cutting (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (HADOOP-497) DataNodes and TaskTrackers should be able to report hostnames and ips relative to customizable network interfaces and nameservers
Date Thu, 07 Sep 2006 20:00:23 GMT
     [ http://issues.apache.org/jira/browse/HADOOP-497?page=all ]

Doug Cutting resolved HADOOP-497.
---------------------------------

    Fix Version/s: 0.6.0
       Resolution: Fixed

I just committed this.  The patch had some spurious changes to imports, and indented four
spaces-per-level rather than two.  I also moved some duplicated code into the DNS utility
class.  Thanks, Lorenzo!

> 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
>             Fix For: 0.6.0
>
>         Attachments: dnsjava-2.0.2.jar, net-dns.patch, 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

        

Mime
View raw message