[
https://issues.apache.org/jira/browse/HADOOP-5276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Amar Kamat updated HADOOP-5276:
-------------------------------
Attachment: HADOOP-5276-v1.3.patch
Updates the patch to trunk. Test patch result :
{code}
[exec] +1 overall.
[exec]
[exec] +1 @author. The patch does not contain any @author tags.
[exec]
[exec] +1 tests included. The patch appears to include 3 new or
modified tests.
[exec]
[exec] +1 javadoc. The javadoc tool did not generate any warning
messages.
[exec]
[exec] +1 javac. The applied patch does not increase the total number
of javac compiler warnings.
[exec]
[exec] +1 findbugs. The patch does not introduce any new Findbugs
warnings.
[exec]
[exec] +1 Eclipse classpath. The patch retains Eclipse classpath
integrity.
[exec]
[exec] +1 release audit. The applied patch does not increase the
total number of release audit warnings.
{code}
> 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
> Priority: Critical
> 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.
