[
https://issues.apache.org/jira/browse/SPARK-12299?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Or resolved SPARK-12299.
-------------------------------
Resolution: Fixed
Assignee: Bryan Cutler
Fix Version/s: 2.0.0
> Remove history serving functionality from standalone Master
> -----------------------------------------------------------
>
> Key: SPARK-12299
> URL: https://issues.apache.org/jira/browse/SPARK-12299
> Project: Spark
> Issue Type: Sub-task
> Components: Deploy
> Affects Versions: 1.0.0
> Reporter: Andrew Or
> Assignee: Bryan Cutler
> Fix For: 2.0.0
>
>
> The standalone Master currently continues to serve the historical UIs of
> applications that have completed and enabled event logging. This poses
> problems, however, if the event log is very large, e.g. SPARK-6270. The
> Master might OOM or hang while it rebuilds the UI, rejecting applications in
> the mean time.
> Personally, I have had to make modifications in the code to disable this
> myself, because I wanted to use event logging in standalone mode for
> applications that produce a lot of logging.
> Removing this from the Master would simplify the process significantly. This
> issue supersedes SPARK-12062.
--
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
