hadoop-mapreduce-issues mailing list archives

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

    [ https://issues.apache.org/jira/browse/MAPREDUCE-5674?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13845758#comment-13845758

Chris Nauroth commented on MAPREDUCE-5674:

Hi, Chuan.  There is another similar method in {{TypeConverter}} that converts a YARN {{ApplicationReport}}
to a {{JobStatus}}.  That one is setting start time, but not finish time.  Do you want to
fix that one too?

For the test, do you want to add an assertion that {{jobStatus.getFinishTime()}} has the expected

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