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 "Devaraj Das (JIRA)" <ji...@apache.org> on 2009/02/24 07:50:01 UTC

[jira] Resolved: (HADOOP-5276) Upon a lost tracker, the task's start time is reset to 0

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

Devaraj Das resolved HADOOP-5276.
---------------------------------

       Resolution: Fixed
    Fix Version/s: 0.21.0
         Assignee: Amar Kamat
     Hadoop Flags: [Reviewed]

I just committed this. Thanks, Amar!

> Upon a lost tracker, the task's start time is reset to 0
> --------------------------------------------------------
>
>                 Key: HADOOP-5276
>                 URL: https://issues.apache.org/jira/browse/HADOOP-5276
>             Project: Hadoop Core
>          Issue Type: Bug
>          Components: mapred
>            Reporter: Amar Kamat
>            Assignee: Amar Kamat
>            Priority: Critical
>             Fix For: 0.21.0
>
>         Attachments: HADOOP-5276-v1.1.patch, HADOOP-5276-v1.2.patch, HADOOP-5276-v1.3.patch
>
>
> Upon lost tracker, the JIP (via JobTracker.lostTracker() -> JobInProgress.failedTask()) hand crafts task status (marking the attempt as KILLED) and updates the JobInProgress (via JobInProgress.updateTaskStatus()). This status contains the attempt start time as 0. One major impact would be that the listener will overwrite the last start time value with the new one and hence the start tiem will get garbled.

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