[
https://issues.apache.org/jira/browse/SPARK-17243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15437668#comment-15437668
]
Alex Bozarth edited comment on SPARK-17243 at 8/25/16 9:05 PM:
---------------------------------------------------------------
I'm not sure I agree that this should be a blocker, but I was actually planning
on filing a JIRA and starting work on a pr next month (September) that will
switch the history server to only load application data when an application ui
is opened and only loading application metadata on the initial load of the
history server. This is just one of many problems that would be fixed by such a
change. I won't have the bandwidth to start working on it for another week or
two though.
tl;dr I plan to fix this but not until next month
was (Author: ajbozarth):
I'm not sure I agree that this should be a blocker, but I was actually planning
on filing a JIRA and starting work on a pr next month (September) that will
switch the history server to only load application data when an application ui
is opened and only loading application metadata on the initial load of the
history server. This is just one of many problems that would be fixed by such a
change. I won't have the bandwidth to start working on it for another week or
two though.
> Spark 2.0 history server summary page gets stuck at "loading history summary"
> with 10K+ application history
> -----------------------------------------------------------------------------------------------------------
>
> Key: SPARK-17243
> URL: https://issues.apache.org/jira/browse/SPARK-17243
> Project: Spark
> Issue Type: Bug
> Components: Web UI
> Affects Versions: 2.0.0
> Environment: Linux
> Reporter: Gang Wu
> Priority: Blocker
>
> The summary page of Spark 2.0 history server web UI keep displaying "Loading
> history summary..." all the time and crashes the browser when there are more
> than 10K application history event logs on HDFS.
> I did some investigation, "historypage.js" file sends a REST request to
> /api/v1/applications endpoint of history server REST endpoint and gets back
> json response. When there are more than 10K applications inside the event log
> directory it takes forever to parse them and render the page. When there are
> only hundreds or thousands of application history it is running fine.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
