hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mohammad Shahid Khan (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (MAPREDUCE-6419) JobHistoryServer doesn't sort properly based on Job ID when Job id's exceed 9999
Date Wed, 23 Dec 2015 18:58:46 GMT

     [ https://issues.apache.org/jira/browse/MAPREDUCE-6419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Mohammad Shahid Khan updated MAPREDUCE-6419:
--------------------------------------------
    Attachment: MAPREDUCE-6419_v3.patch

> 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
>         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)

Mime
View raw message