hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "alan wootton (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-197) Hook InetAddress.getLocalHost().getHostName() to support cluster simulatation.
Date Fri, 05 May 2006 23:25:28 GMT
    [ http://issues.apache.org/jira/browse/HADOOP-197?page=comments#action_12378168 ] 

alan wootton commented on HADOOP-197:

I thought of adding it to conf. That is logical. It's just that Configuration is so, ...,
'clean' and I didn't want to start dumping stuff into to. But, since you bring it up: I send
a patch with InetAddress.getLocalHost().getHostName() implemented as a method named 'getLocalHost'

> 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: mapred, dfs
>  Environment: all
>     Reporter: alan wootton
>     Priority: Minor
>  Attachments: InetAddressWrapper.patch, conf_getHostName.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

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message