hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Arun C Murthy (JIRA)" <j...@apache.org>
Subject [jira] Updated: (HADOOP-2022) Task times are not saved correctly (bug in hadoop-1874)
Date Thu, 11 Oct 2007 19:52:50 GMT

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

Arun C Murthy updated HADOOP-2022:
----------------------------------

    Resolution: Fixed
        Status: Resolved  (was: Patch Available)

I just committed this. Thanks, Amar!

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


Mime
View raw message