You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "duyanghao (JIRA)" <ji...@apache.org> on 2017/08/12 03:10:02 UTC
[jira] [Commented] (SPARK-18085) SPIP: Better History Server
scalability for many / large applications
[ https://issues.apache.org/jira/browse/SPARK-18085?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16124421#comment-16124421 ]
duyanghao commented on SPARK-18085:
-----------------------------------
[~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-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org