You are viewing a plain text version of this content. The canonical link for it is here.
Posted to mapreduce-dev@hadoop.apache.org by "Tao Jie (JIRA)" <ji...@apache.org> on 2018/01/17 03:03:01 UTC
[jira] [Created] (MAPREDUCE-7040) Job order in HistoryServer is not
always correct
Tao Jie created MAPREDUCE-7040:
----------------------------------
Summary: Job order in HistoryServer is not always correct
Key: MAPREDUCE-7040
URL: https://issues.apache.org/jira/browse/MAPREDUCE-7040
Project: Hadoop Map/Reduce
Issue Type: Bug
Components: jobhistoryserver
Affects Versions: 2.8.2
Reporter: Tao Jie
Now in JobHistoryServer, jobs are ordered by JobID in a datatable. JobID here is interpreted as a string rather than parsing the id number from the JobID. As a result, jobID [job_1516090502319_|http://cmhtj1:19888/jobhistory/job/job_1516090502319_0001]9999 is alway in front of [job_1516090502319_|http://cmhtj1:19888/jobhistory/job/job_1516090502319_0001]10123 while the later is the newer job.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: mapreduce-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: mapreduce-dev-help@hadoop.apache.org