[
https://issues.apache.org/jira/browse/MAPREDUCE-725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12728305#action_12728305
]
Matei Zaharia commented on MAPREDUCE-725:
-----------------------------------------
In fact, it might be even better if there were methods called
JobInProgress.numSpeculativeMaps and JobInProgress.numSpeculativeReduces that
say how many speculative tasks the job wants to launch. Knowing this number is
useful when you need to make high-memory slots for the speculative tasks, or
when you need to preempt tasks from other jobs.
> CapacityScheduler.TaskSchedulingMgr.hasSpeculativeTask bypasses HADOOP-2141
> ---------------------------------------------------------------------------
>
> Key: MAPREDUCE-725
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-725
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: contrib/capacity-sched
> Reporter: Arun C Murthy
> Priority: Critical
>
> CapacityScheduler.TaskSchedulingMgr.hasSpeculativeTask has a duplicate of the
> old speculation code (pre HADOOP-2141) which needs to be fixed in-order for
> speculation to work correctly.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
