You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-dev@hadoop.apache.org by "Vinod K V (JIRA)" <ji...@apache.org> on 2009/05/29 09:04:45 UTC

[jira] Resolved: (HADOOP-5934) testHighRamJobWithSpeculativeExecution needs some changes

     [ https://issues.apache.org/jira/browse/HADOOP-5934?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Vinod K V resolved HADOOP-5934.
-------------------------------

    Resolution: Duplicate

Incorporated in HADOOP-5884.

> testHighRamJobWithSpeculativeExecution needs some changes
> ---------------------------------------------------------
>
>                 Key: HADOOP-5934
>                 URL: https://issues.apache.org/jira/browse/HADOOP-5934
>             Project: Hadoop Core
>          Issue Type: Bug
>          Components: contrib/capacity-sched
>            Reporter: Hemanth Yamijala
>
> There are some problems I noticed with TestCapacityScheduler.testHighRamJobWithSpeculativeExecution():
> - Comments are out of sync. For e.g. we say "// 2 map and 2 reduce slots" and start a cluster with 3 maps and reduces
> - In the test for reduces with speculative execution, the second job submitted is submitting high RAM maps
> - In the normal job's reduces, the memory is set as 1 * 104, instead of 1* 1024
> - Test should check for pendingReduces instead of pendingMaps in the reduce speculation case.

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