[
https://issues.apache.org/jira/browse/SPARK-4598?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14228684#comment-14228684
]
Josh Rosen commented on SPARK-4598:
-----------------------------------
Actually, it might be pretty hard to trim down the memory usage via scala.xml
tricks. Adding some functionality to return the stage table information as CSV
data might be a cleaner way to handle this. This doesn't necessarily imply
using AJAX requests to load the data from the backend; we could just dump the
CSV data into a script tag and load it via Javascript. We might be able to
hide all of this complexity behind the StageTableBase class, so we could this
change to a small section of the code.
> Paginate stage page to avoid OOM with > 100,000 tasks
> -----------------------------------------------------
>
> Key: SPARK-4598
> URL: https://issues.apache.org/jira/browse/SPARK-4598
> Project: Spark
> Issue Type: Bug
> Components: Spark Core
> Affects Versions: 1.2.0
> Reporter: meiyoula
> Priority: Critical
>
> In HistoryServer stage page, clicking the task href in Description, it occurs
> the GC error. The detail error message is:
> 2014-11-17 16:36:30,851 | WARN | [qtp1083955615-352] | Error for
> /history/application_1416206401491_0010/stages/stage/ |
> org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:590)
> java.lang.OutOfMemoryError: GC overhead limit exceeded
> 2014-11-17 16:36:30,851 | WARN | [qtp1083955615-364] | handle failed |
> org.eclipse.jetty.io.nio.SelectChannelEndPoint.handle(SelectChannelEndPoint.java:697)
> java.lang.OutOfMemoryError: GC overhead limit exceeded
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
