hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sanjay Dahiya (JIRA)" <j...@apache.org>
Subject [jira] Updated: (HADOOP-588) JobTracker History bug - kill() ed tasks are logged wrongly as finished.
Date Tue, 10 Oct 2006 08:23:20 GMT
     [ http://issues.apache.org/jira/browse/HADOOP-588?page=all ]

Sanjay Dahiya updated HADOOP-588:
---------------------------------

    Attachment: Hadoop-588.patch

This patch fixes 2 issues with jobtracker history logging. 
1. JobInProgress.kill() now logs jobs as failed instead of finished. 
2. For failed task attempts, the failure is not propagated to Task page until the taskAttempts
fails max(4) no of times. Earlier the failed task attempt's error would be visible on task
page even when a subsequent task attempt succeeded, which was confusing. 


> JobTracker History bug - kill() ed tasks are logged wrongly as finished.
> ------------------------------------------------------------------------
>
>                 Key: HADOOP-588
>                 URL: http://issues.apache.org/jira/browse/HADOOP-588
>             Project: Hadoop
>          Issue Type: Bug
>          Components: mapred
>    Affects Versions: 0.7.0
>            Reporter: Sanjay Dahiya
>         Assigned To: Sanjay Dahiya
>             Fix For: 0.7.1
>
>         Attachments: Hadoop-588.patch
>
>
> JobInProgress.kill() logs jobs as finished in jobtracker history, whereas they should
be logged as failed. 

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message