[
https://issues.apache.org/jira/browse/SPARK-18085?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16125150#comment-16125150
]
duyanghao edited comment on SPARK-18085 at 8/14/17 2:31 AM:
------------------------------------------------------------
[~vanzin] so what you mean is that your project has done nothing about loading
large event logs(100G+) and loading history summary page when the event log
directory is large at the first time.What you have done is for quick loading
logs for subsequent use.
I am afraid that only solves one part of above problems(for subsequent use),one
more important problem is that how to quick load logs at the first time.
was (Author: duyanghao):
[~vanzin] so what you mean is that your project has done nothing about loading
large event logs(100G+) and loading history summary page when the event log
directory is large at the first time.What you have done is for quick loading
logs for subsequent use.
> SPIP: Better History Server scalability for many / large applications
> ---------------------------------------------------------------------
>
> Key: SPARK-18085
> URL: https://issues.apache.org/jira/browse/SPARK-18085
> Project: Spark
> Issue Type: Umbrella
> Components: Spark Core, Web UI
> Affects Versions: 2.0.0
> Reporter: Marcelo Vanzin
> Labels: SPIP
> Attachments: spark_hs_next_gen.pdf
>
>
> It's a known fact that the History Server currently has some annoying issues
> when serving lots of applications, and when serving large applications.
> I'm filing this umbrella to track work related to addressing those issues.
> I'll be attaching a document shortly describing the issues and suggesting a
> path to how to solve them.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
