[
https://issues.apache.org/jira/browse/MAPREDUCE-5052?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13822714#comment-13822714
]
Hadoop QA commented on MAPREDUCE-5052:
--------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12613882/MAPREDUCE-5052.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{color:green}+1 eclipse:eclipse{color}. The patch built with
eclipse:eclipse.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 1.3.9) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:red}-1 core tests{color}. The patch failed these unit tests in
hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-app
hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-common
hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-hs
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager:
org.apache.hadoop.mapreduce.v2.app.TestRMContainerAllocator
org.apache.hadoop.mapreduce.v2.jobhistory.TestFileNameIndexUtils
org.apache.hadoop.mapreduce.v2.hs.webapp.TestHsWebServicesJobsQuery
org.apache.hadoop.mapreduce.v2.hs.webapp.TestHsWebServicesJobs
org.apache.hadoop.yarn.server.resourcemanager.webapp.TestRMWebApp
org.apache.hadoop.yarn.server.resourcemanager.webapp.TestRMWebServicesApps
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/4199//testReport/
Console output:
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/4199//console
This message is automatically generated.
> 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
> 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#6144)
