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 "zhaoyunjiong (JIRA)" <ji...@apache.org> on 2013/10/14 10:00:47 UTC
[jira] [Updated] (MAPREDUCE-5541) Improved algorithm for whether
need speculative task
[ https://issues.apache.org/jira/browse/MAPREDUCE-5541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
zhaoyunjiong updated MAPREDUCE-5541:
------------------------------------
Attachment: MAPREDUCE-5541-branch-1.2.configurable.patch
This patch can use mapred.job.speculative.progress and mapred.job.speculative.factor to control when a job need speculative tasks.
> Improved algorithm for whether need speculative task
> ----------------------------------------------------
>
> Key: MAPREDUCE-5541
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-5541
> Project: Hadoop Map/Reduce
> Issue Type: Improvement
> Components: mrv1
> Affects Versions: 1.2.1
> Reporter: zhaoyunjiong
> Assignee: zhaoyunjiong
> Fix For: 1.2.2
>
> Attachments: MAPREDUCE-5541-branch-1.2.configurable.patch, MAPREDUCE-5541-branch-1.2.patch
>
>
> Most of time, tasks won't start running at same time.
> In this case hasSpeculativeTask in TaskInProgress not working very well.
> Some times, some tasks just start running, and scheduler already decide it need speculative task to run.
> And this waste a lot of resource.
--
This message was sent by Atlassian JIRA
(v6.1#6144)