hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chuan Liu (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (MAPREDUCE-5674) Missing start and finish time in mapred.JobStatus
Date Wed, 11 Dec 2013 22:14:07 GMT

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

Chuan Liu updated MAPREDUCE-5674:

    Attachment: MAPREDUCE-5674.2.patch

Nice catch! I did not check the other method when preparing the first patch. Attach a new
one that also fixes the other method and adds some more asserts to the tests.

> Missing start and finish time in mapred.JobStatus
> -------------------------------------------------
>                 Key: MAPREDUCE-5674
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-5674
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>    Affects Versions: 3.0.0
>            Reporter: Chuan Liu
>            Assignee: Chuan Liu
>         Attachments: MAPREDUCE-5674.2.patch, MAPREDUCE-5674.patch
> The JobStatus obtained from the JobClient or runningJob has no start or finish time for
the job -- the start and finish time is always 0. This is a regression with respect to 1.0
mapreduce client and JobStatus API. This can also lead to regressions in downstream projects.
For example, we discovered the problem in webhcat that the jobstatus for mapreduce job submmited
to webhcat always reports start time as 0.

This message was sent by Atlassian JIRA

View raw message