You are viewing a plain text version of this content. The canonical link for it is here.

Posted to mapreduce-issues@hadoop.apache.org by "Balaji Rajagopalan (JIRA)" <ji...@apache.org> on 2010/07/13 09:15:51 UTC

[jira] Commented: (MAPREDUCE-1934) Timing issue with Distributed Cache testcases for already automated (herriot ) test scenarios.

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

Balaji Rajagopalan commented on MAPREDUCE-1934:
-----------------------------------------------

two things you have wrong dependency, second 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 

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