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 "Amar Kamat (JIRA)" <ji...@apache.org> on 2007/10/11 12:23:50 UTC

[jira] Updated: (HADOOP-2022) Task times are not saved correctly (bug in hadoop-1874)

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

Amar Kamat updated HADOOP-2022:
-------------------------------

    Attachment: HADOOP-2022.patch

> Task times are not saved correctly (bug in hadoop-1874)
> -------------------------------------------------------
>
>                 Key: HADOOP-2022
>                 URL: https://issues.apache.org/jira/browse/HADOOP-2022
>             Project: Hadoop
>          Issue Type: Bug
>          Components: mapred
>    Affects Versions: 0.15.0
>            Reporter: Devaraj Das
>            Assignee: Amar Kamat
>            Priority: Blocker
>             Fix For: 0.15.0
>
>         Attachments: HADOOP-2022.patch
>
>
> In HADOOP-1874, a new taskstatus object is created for successful tasks. However, in the new taskstatus object, the timestamps for the start/end of the various phases are not filled. In the new status object, the timestamps should be set from the old status object. The problem can be easily seen if the taskdetails.jsp is accessed.

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