[ https://issues.apache.org/jira/browse/SPARK-18085?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16039223#comment-16039223 ]
Marcelo Vanzin commented on SPARK-18085: ---------------------------------------- Yes, https://github.com/vanzin/spark/commits/shs-ng/HEAD should always contain the most up-to-date code. To actually try the leveldb backend you need to set a new configuration in the SHS (check config.scala in the o.a.s.history package). > 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 > 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.3.15#6346) --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org For additional commands, e-mail: issues-h...@spark.apache.org