hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Iyappan Srinivasan (JIRA)" <j...@apache.org>
Subject [jira] Commented: (MAPREDUCE-1934) Timing issue with Distributed Cache testcases for already automated (herriot ) test scenarios.
Date Tue, 13 Jul 2010 07:29:50 GMT

    [ https://issues.apache.org/jira/browse/MAPREDUCE-1934?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12887681#action_12887681
] 

Iyappan Srinivasan commented on MAPREDUCE-1934:
-----------------------------------------------

you have wrong dependency

[Iyappan]  I have added the right dependency. Basically, it is for waitForTTStop() and waitForTTStart()
availablity.

 since you are starting/stopping all the deamons it should be done at cluster level, there
is no need to write new code. 
Instead use this HadoopDaemonRemoteCluster::stop 

[Iyappan] - Only tasktrackers and not all daemons are stopped and started. Since, the HadoopDaemonRemoteCluster::stop()
stops al lthe daemons, it cannot be used.

> Timing issue with Distributed Cache testcases for already automated (herriot ) test scenarios.
> ----------------------------------------------------------------------------------------------
>
>                 Key: MAPREDUCE-1934
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-1934
>             Project: Hadoop Map/Reduce
>          Issue Type: Test
>            Reporter: Iyappan Srinivasan
>            Assignee: Iyappan Srinivasan
>         Attachments: DistributedCacheTiming.patch
>
>
> Sometimes, Distributed cache testcases fail becuse the tasktrackers dont come up fast
enough after kill and start. This needs to be fixed.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message