[
https://issues.apache.org/jira/browse/MAPREDUCE-6419?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15070651#comment-15070651
]
Hudson commented on MAPREDUCE-6419:
-----------------------------------
FAILURE: Integrated in Hadoop-trunk-Commit #9022 (See
[https://builds.apache.org/job/Hadoop-trunk-Commit/9022/])
MAPREDUCE-6419. JobHistoryServer doesn't sort properly based on Job ID
(rohithsharmaks: rev a308e86621b1a7692fe1004ed14c919fdaba03cd)
*
hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-hs/src/test/java/org/apache/hadoop/mapreduce/v2/hs/webapp/TestHSWebApp.java
*
hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-hs/src/main/java/org/apache/hadoop/mapreduce/v2/hs/webapp/HsTasksPage.java
*
hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-hs/src/main/java/org/apache/hadoop/mapreduce/v2/hs/webapp/HsTaskPage.java
* hadoop-mapreduce-project/CHANGES.txt
> JobHistoryServer doesn't sort properly based on Job ID when Job id's exceed
> 9999
> --------------------------------------------------------------------------------
>
> Key: MAPREDUCE-6419
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-6419
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: webapps
> Affects Versions: 2.7.0
> Reporter: Devaraj K
> Assignee: Mohammad Shahid Khan
> Fix For: 2.8.0
>
> Attachments: MAPREDUCE-6419.patch, MAPREDUCE-6419_v2.patch,
> MAPREDUCE-6419_v3.patch
>
>
> When Job id's exceed 9999, JobHistoryServer is not sorting properly based on
> the Job ID. It is mixing the jobs having > 9999 with other jobs considering
> only the first four digits of the job id. The same problem could exist for
> Job Map tasks and Reduce tasks table as well.
> It is similar to the issue YARN-3840 exists for YARN.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
