[jira] Updated: (HADOOP-197) Hook InetAddress.getLocalHost().getHostName() to support cluster simulatation.

["alan wootton (JIRA)" <ji...@apache.org>]

     [ http://issues.apache.org/jira/browse/HADOOP-197?page=all ]

alan wootton updated HADOOP-197:
--------------------------------

    Attachment: InetAddressWrapper.patch

> Hook InetAddress.getLocalHost().getHostName() to support cluster simulatation.
> ------------------------------------------------------------------------------
>
>          Key: HADOOP-197
>          URL: http://issues.apache.org/jira/browse/HADOOP-197
>      Project: Hadoop
>         Type: Improvement

>   Components: dfs, mapred
>  Environment: all
>     Reporter: alan wootton
>     Priority: Minor
>  Attachments: InetAddressWrapper.patch
>
> I have been running a simulation for weeks now (and also a 30 machine crawl). To make it work I need to sometimes 
> let DataNodes, and TaskTrackers think they have a different machine-name than the one in InetAddress.getLocalHost()
> The patch is:
> 1) replace InetAddress.getLocalHost().getHostName() with xxxx
> 	1.a)xxxx could be "conf.get("inetaddress.localhost.name",InetAddress.getLocalHost().getHostName())"
> 	1.b)or, xxxx could be a static call, I chose the latter: "InetAddressWrapper.getLocalHostName(conf)"
> 2) InetAddressWrapper.getLocalHostName(conf) checks the config for a hostname, and then calls InetAddress.getLocalHost().getHostName()
> There's 3 places where it happens:
> DataNode
> DFSClient
> TaskTracker
> I did not patch the two tests that call InetAddress because they are not really using hostname.

-- 
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