[
https://issues.apache.org/jira/browse/SPARK-19814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon King closed SPARK-19814.
--
Resolution: Duplicate
Looks like it's wrong to characterize this as a bug -- couldn't identify an
actu
[
https://issues.apache.org/jira/browse/SPARK-19814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15894984#comment-15894984
]
Simon King commented on SPARK-19814:
OK, let me leave this open over the weekend to s
[
https://issues.apache.org/jira/browse/SPARK-19814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15894948#comment-15894948
]
Simon King commented on SPARK-19814:
Sean, I think that giving more memory only delay
[
https://issues.apache.org/jira/browse/SPARK-19814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon King updated SPARK-19814:
---
Attachment: SparkHistoryCPUandRAM.png
Graph showing CPU usage (top) and RSS RAM (bottom). Note the on
[
https://issues.apache.org/jira/browse/SPARK-19814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon King updated SPARK-19814:
---
Description:
Spark History Server runs out of memory, gets into GC thrash and eventually
becomes unr
Simon King created SPARK-19814:
--
Summary: Spark History Server Out Of Memory / Extreme GC
Key: SPARK-19814
URL: https://issues.apache.org/jira/browse/SPARK-19814
Project: Spark
Issue Type: Bug