hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ray Chiang (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MAPREDUCE-6222) Add server-side pagination to JobHistoryServer tasks page
Date Wed, 10 Jun 2015 21:51:01 GMT

    [ https://issues.apache.org/jira/browse/MAPREDUCE-6222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14581134#comment-14581134

Ray Chiang commented on MAPREDUCE-6222:

For 2) above, MAPREDUCE-6394 has been created.  Even with MAPREDUCE-6376 and MAPREDUCE-6394,
it turns out that the Javascript UI is pretty slow on jobs with a really large number of tasks
(~10 seconds to sort 404k tasks, ~20 seconds to sort 751k tasks).  So, this JIRA could still
be desirable for some.

> Add server-side pagination to JobHistoryServer tasks page
> ---------------------------------------------------------
>                 Key: MAPREDUCE-6222
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-6222
>             Project: Hadoop Map/Reduce
>          Issue Type: Sub-task
>            Reporter: Andrew Johnson
>            Assignee: Ray Chiang
>              Labels: BB2015-05-TBR
>         Attachments: JHS New Display Top.png, JHS Original Display Top.png, MAPREDUCE-6222.001.patch,
MAPREDUCE-6222.002.patch, MAPREDUCE-6222.003.patch, MAPREDUCE-6222.005.patch, MAPREDUCE-6222.006.patch,
MAPREDUCE-6222.007.patch, MAPREDUCE-6222.008.patch, MAPREDUCE-6222.009.patch, Screen Shot
2015-05-20 at 11.16.25 AM.png, head.jhist, historyserver_jstack.txt
> I'm encountering an issue with the Mapreduce HistoryServer processing the history files
for large jobs.  This has come up several times with for jobs with around 60000 total tasks.
 When the HistoryServer loads the .jhist file from HDFS for a job of that size (which is usually
around 500 Mb), the HistoryServer's CPU usage spiked and the UI became unresponsive.  After
about 10 minutes I restarted the HistoryServer and it was behaving normally again.
> The cluster is running CDH 5.3 (2.5.0-cdh5.3.0).  I've attached the output of jstack
from a time this was occurring.

This message was sent by Atlassian JIRA

View raw message