[
https://issues.apache.org/jira/browse/HADOOP-4981?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sreekanth Ramakrishnan updated HADOOP-4981:
-------------------------------------------
Attachment: HADOOP-4981-2.patch
Attaching new patch incorporating Hemanths comments:
* Added a new check to see if the task has already run on the same tracker
while returning if job has speculative task or not.
* Added documentation to methods, added summary to the two test cases.
* Modified {{testHighRamJobWithSpeculativeExecution()}} to have two cases, one
with speculative maps and other with speculative reduces.
> Prior code fix in Capacity Scheduler prevents speculative execution in jobs
> ---------------------------------------------------------------------------
>
> Key: HADOOP-4981
> URL: https://issues.apache.org/jira/browse/HADOOP-4981
> Project: Hadoop Core
> Issue Type: Bug
> Components: contrib/capacity-sched
> Reporter: Vivek Ratan
> Attachments: 4981.1.patch, 4981.2.patch, HADOOP-4981-1.patch,
> HADOOP-4981-2.patch
>
>
> As part of the code fix for HADOOP-4035, the Capacity Scheduler obtains a
> task from JobInProgress (calling obtainNewMapTask() or obtainNewReduceTask())
> only if the number of pending tasks for a job is greater than zero (see the
> if-block in TaskSchedulingMgr.getTaskFromJob()). So, if a job has no pending
> tasks and only has running tasks, it will never be given a slot, and will
> never have a chance to run a speculative task.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
