[MAPREDUCE-5674] Missing start and finish time in mapred.JobStatus

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.2.0, 3.0.0-alpha1
• Fix Version/s: 2.3.0
• Component/s: client
• Target Version/s: 2.3.0
• Hadoop Flags: Reviewed
• Assignee: Chuan Liu
• Reporter: Chuan Liu
• Created: 07/Dec/13 01:48
• Updated: 12/May/16 18:23
• Resolved: 12/Dec/13 18:41

Description

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.