hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Allen Wittenauer (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (MAPREDUCE-2062) speculative execution is too aggressive under certain conditions
Date Wed, 30 Jul 2014 23:57:40 GMT

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

Allen Wittenauer resolved MAPREDUCE-2062.
-----------------------------------------

    Resolution: Fixed

Spec exec got majorly overhauled. Closing.

> speculative execution is too aggressive under certain conditions
> ----------------------------------------------------------------
>
>                 Key: MAPREDUCE-2062
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-2062
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: jobtracker
>         Environment: hadoop-20 with HADOOP-2141
>            Reporter: Joydeep Sen Sarma
>
> The function canBeSpeculated has subtle bugs that cause too much speculation in certain
cases.
> - it compares the current progress of the task with the last observed mean of all the
tasks. if only one task is in question - then the progress rate decays as time progresses
(in the absence of updates) and std-dev is zero. So a job with a single reducer or mapper
is almost always speculated.
> - is only a single task has reported progress - then the stddev is zero. so other tasks
may be speculated aggressively.
> - several tasks take a while to report progress initially. they seem to get speculated
as soon as speculative-lag is over. the lag should be configurable at the minimum.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message