hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Arun C Murthy (JIRA)" <j...@apache.org>
Subject [jira] Updated: (HADOOP-1050) Do not count lost tasktracker against the job
Date Thu, 19 Apr 2007 20:50:15 GMT

     [ 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_20070419_2.patch

Here is a reasonably well tested patch which helps to distinguish between *failed* tasks (i.e.
bona-fide task 'error') and *killed* tasks (killed by the framework for no fault of their
own e.g. lost task-trackers). With this in place it's then straight-forward to ensure that
'killed' tasks do not count against the job, thus not penalizing it.

Other than that this patch contains some enchancements to jobdetails.jsp/jobfailures.jsp to
show the same information on the web-ui...


> 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
>             Fix For: 0.13.0
>
>         Attachments: HADOOP-1050_20070405_1.patch, HADOOP-1050_20070419_2.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.


Mime
View raw message