hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Karthik Kambatla (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (MAPREDUCE-6066) Speculative attempts should not run on the same node as their original attempt
Date Wed, 03 Sep 2014 21:41:53 GMT

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

Karthik Kambatla updated MAPREDUCE-6066:
----------------------------------------
    Affects Version/s:     (was: 3.0.0)
                       2.5.0

> 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
>            Reporter: Todd Lipcon
>         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
(v6.3.4#6332)

Mime
View raw message