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 "Arun C Murthy (JIRA)" <ji...@apache.org> on 2007/04/04 22:58:32 UTC

[jira] Updated: (HADOOP-1050) Do not count lost tasktracker against the job

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

Arun C Murthy updated HADOOP-1050:
----------------------------------

    Attachment: HADOOP-1050_20070405_1.patch

Here's a patch while I continue testing... appreciate any f/b.

This patch ensures that the framework distinguishes between 'failed' tasks and tasks 'killed' because of framework errors (e.g lost task-trackers) and thus does not unfairly abort TIPs and hence jobs due to no fault of their own.

> Do not count lost tasktracker against the job
> ---------------------------------------------
>
>                 Key: HADOOP-1050
>                 URL: https://issues.apache.org/jira/browse/HADOOP-1050
>             Project: Hadoop
>          Issue Type: Bug
>          Components: mapred
>            Reporter: Arun C Murthy
>         Assigned To: Arun C Murthy
>         Attachments: HADOOP-1050_20070405_1.patch
>
>
> Equating a task failure to the one caused by a lost tasktracker is unfair on the job; in extreme cases it leads to a job being killed since a TIP could fail.

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