[
https://issues.apache.org/jira/browse/SPARK-18085?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16124421#comment-16124421
]
duyanghao edited comment on SPARK-18085 at 8/12/17 3:11 AM:
------------------------------------------------------------
[~vanzin] Could you have a summary of your progress(solved problems and
unsolved problems) since we all have the same problems for loading large event
logs(100G+) and loading history summary page when the event log directory is
large.
We all want to know how good your solution is(of course from your test results)
and your plans to do it.
was (Author: duyanghao):
[~vanzin] Could you have a summary of your progress(solved problems and
unsolved problems) since we all have the same problems for loading large event
logs(100G+) and loading history summary page when the event log directory is
large.
We all want to know how good your solution is(of course from your test results)?
> 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
