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] Commented: (HADOOP-214) ClusterTestDFS fails
Date Fri, 12 May 2006 20:10:09 GMT
    [ http://issues.apache.org/jira/browse/HADOOP-214?page=comments#action_12383263 ] 

Doug Cutting commented on HADOOP-214:

Having to change the hosts file for a test is not great.

Perhaps we could instead just alter Java to resolve hostnames differently while testing?


> ClusterTestDFS fails
> --------------------
>          Key: HADOOP-214
>          URL: http://issues.apache.org/jira/browse/HADOOP-214
>      Project: Hadoop
>         Type: Bug

>   Components: dfs
>     Versions: 0.2.1
>  Environment: local workstation (windows) 
>     Reporter: alan wootton
>  Attachments: fix_clustertestdfs.patch
> The dfs unit tests, from the ant target 'cluster' have been failing. (ClusterTestDFSNamespaceLogging,
ClusterTestDFS). I don't know if anyone but me cares about these tests, but I do. I would
like to write better tests for dns. I think we all need that.
> They have been partially broken since  "test.dfs.same.host.targets.allowed" went away
and replication ceased for these tests. 
> They got really broken when NameNode stopped automatically formatting itself .
> Since they seem to be ignored, I took the liberty of changing how they work.
> The main thing is, you must put this into your hosts file:
>       localhost0
>       localhost1
>       localhost2
>       localhost3
>       localhost4
>       localhost5
>       localhost6
>       localhost7
>       localhost8
>       localhost9
>       localhost10
>       localhost11
>       localhost12
>       localhost13
>       localhost14
>       localhost15
> This way you can start DataNodes, and TaskTrackers (up to 16 of them) with unique hostnames.
> Also, I changed all the places that used to call InetAddress.getLocalHost().getHostName()
to get it from a new method in Configuration (this issue is the same as http://issues.apache.org/jira/browse/HADOOP-197

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