You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Josh Rosen (JIRA)" <ji...@apache.org> on 2016/01/18 21:50:40 UTC
[jira] [Commented] (SPARK-12299) Remove history serving
functionality from standalone Master
[ https://issues.apache.org/jira/browse/SPARK-12299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15105817#comment-15105817 ]
Josh Rosen commented on SPARK-12299:
------------------------------------
I'm not actively working on this, so this is up-for-grabs if anyone wants to do this. Note that along with removing this functionality, it would be good to clean up the APIs in the UI which were necessary only to support this deprecated functionality.
> 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: Josh Rosen
>
> 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-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org