[
https://issues.apache.org/jira/browse/MAPREDUCE-6066?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Turner Eagles resolved MAPREDUCE-6066.
-----------------------------------------------
Resolution: Duplicate
> 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: 2.5.0, 2.6.0
> Reporter: Todd Lipcon
> Priority: Major
> Attachments: conf.xml
>
>
> 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
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
