[
https://issues.apache.org/jira/browse/MAPREDUCE-6222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14543988#comment-14543988
]
Ray Chiang commented on MAPREDUCE-6222:
---------------------------------------
Any form of pagination will break UI based searching and sorting. But without
a UI rewrite that includes built-in search functionality (i.e. Web 2.0 style),
I'm not sure I see a better solution. With the configurable options, it's easy
enough to set the pagination value quite large (say setting
mapreduce.jobhistory.tasks.pagination.tasks-per-page to 500, i.e. 500k tasks)
which would keep things equivalent to the previous UI (with the pagination
links still added).
I'm seeing closer to 30 seconds and 60 seconds for my JHS (matching the timing
for this JIRA). In general, we're going to have someone complaining about the
UI when the responsiveness is over their expectation level.
> HistoryServer Hangs Processing Large Jobs
> -----------------------------------------
>
> Key: MAPREDUCE-6222
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-6222
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> 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, 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
(v6.3.4#6332)
