You are viewing a plain text version of this content. The canonical link for it is here.

Posted to common-dev@hadoop.apache.org by "Owen O'Malley (JIRA)" <ji...@apache.org> on 2007/06/29 21:51:04 UTC

[jira] Resolved: (HADOOP-1542) Incorrect task/tip being scheduled (looks like speculative execution)

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

Owen O'Malley resolved HADOOP-1542.
-----------------------------------

    Resolution: Fixed

HADOOP-1440 needs to be re-created as a new issue, but this bug is fixed.

> Incorrect task/tip being scheduled (looks like speculative execution)
> ---------------------------------------------------------------------
>
>                 Key: HADOOP-1542
>                 URL: https://issues.apache.org/jira/browse/HADOOP-1542
>             Project: Hadoop
>          Issue Type: Bug
>          Components: mapred
>    Affects Versions: 0.14.0
>            Reporter: Nigel Daley
>            Assignee: Owen O'Malley
>            Priority: Blocker
>             Fix For: 0.14.0
>
>         Attachments: jobtracker.log, namenode.log
>
>
> The change in HADOOP-1440 broke map/reduce by breaking the assumption that Task.getPartition() corresponded to the JobInProgress.map[] order. 
> Currently JobInProgress.findNewTask uses Task.getPartition as the index of the map to run. This can be a completely different tip, which will cause incorrect tasks to be run, including duplicates of tasks that are already running.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.