[
https://issues.apache.org/jira/browse/MAPREDUCE-5052?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Eagles updated MAPREDUCE-5052:
---------------------------------------
Resolution: Fixed
Fix Version/s: 3.0.0
Target Version/s: 3.0.0, 2.4.0 (was: 2.4.0)
Status: Resolved (was: Patch Available)
+1. Thanks for this patch, Chen.
> Job History UI and web services confusing job start time and job submit time
> ----------------------------------------------------------------------------
>
> Key: MAPREDUCE-5052
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-5052
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: jobhistoryserver, webapps
> Affects Versions: 0.23.6
> Reporter: Kendall Thrapp
> Assignee: Chen He
> Priority: Critical
> Fix For: 3.0.0, 2.4.0
>
> Attachments: MAPREDUCE-5052.patch
>
>
> The "Start Time" column shown on Job History server's main webpage
> (http://<host>:<port>/jobhistory) is actually showing the *submit* time for
> jobs. However, when you drill down to an individual job's page, there the
> "Start Time" really does refer to when the job actually started.
> This also true for the web services REST API, where the Jobs listing returns
> the submit times as "startTime", but the single Job API returns the start
> time as "startTime".
> The two different times being referred to by the same name is confusing.
> However, it is useful to have both times, as the difference between the
> submit time and start time can show how long a job was stuck waiting in a
> queue. The column on the main job history page should be changed to "Submit
> Time" and the individual job's page should show both the submit time and
> start time. The web services REST API should be updated with these changes
> as well.
--
This message was sent by Atlassian JIRA
(v6.1.4#6159)
