[
https://issues.apache.org/jira/browse/MAPREDUCE-6066?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sandy Ryza moved YARN-2491 to MAPREDUCE-6066:
---------------------------------------------
Component/s: (was: scheduler)
scheduler
applicationmaster
Affects Version/s: (was: 3.0.0)
3.0.0
Key: MAPREDUCE-6066 (was: YARN-2491)
Project: Hadoop Map/Reduce (was: Hadoop YARN)
> Speculative attempts should not run on the same node as their original attempt
> ------------------------------------------------------------------------------
>
> Key: MAPREDUCE-6066
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-6066
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: applicationmaster, scheduler
> Affects Versions: 3.0.0
> Reporter: Todd Lipcon
>
> I'm seeing a behavior on trunk with fair scheduler enabled where a
> speculative reduce attempt is getting run on the same node as its original
> attempt. This doesn't make sense -- the main reason for speculative execution
> is to deal with a slow node, so scheduling a second attempt on the same node
> would just make the problem worse if anything.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
