hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Devaraj Das (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-5276) Upon a lost tracker, the task's start time is reset to 0
Date Thu, 12 Mar 2009 16:40:50 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-5276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12681384#action_12681384

Devaraj Das commented on HADOOP-5276:

i committed this patch to branch-0.20 as well.

> 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.

View raw message