[
https://issues.apache.org/jira/browse/MAPREDUCE-6222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14543753#comment-14543753
]
Jason Lowe commented on MAPREDUCE-6222:
---------------------------------------
Doesn't this break searching/sorting in the UI? Our users often sort tasks by
start time, finish time, or elapsed time or search for specific IDs with the
search box.
We are not seeing the HTTP timeouts or minutes of loading with large jobs as
being reported here. A job with around 40,000 tasks loads in about 8 seconds
if it's not in the job history cache. A job with 106,000 tasks takes a bit
less than 30 seconds to load, again if it's not in the cache.
> 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)
