You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Thomas Graves (JIRA)" <ji...@apache.org> on 2016/08/25 16:57:20 UTC
[jira] [Updated] (SPARK-15083) History Server would OOM due to
unlimited TaskUIData in some stages
[ https://issues.apache.org/jira/browse/SPARK-15083?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Thomas Graves updated SPARK-15083:
----------------------------------
Fix Version/s: 2.0.1
> History Server would OOM due to unlimited TaskUIData in some stages
> -------------------------------------------------------------------
>
> Key: SPARK-15083
> URL: https://issues.apache.org/jira/browse/SPARK-15083
> Project: Spark
> Issue Type: Bug
> Components: Web UI
> Affects Versions: 1.5.2, 1.6.0, 2.0.0
> Reporter: Zheng Tan
> Assignee: Alex Bozarth
> Fix For: 2.0.1, 2.1.0
>
> Attachments: Screen Shot 2016-05-01 at 3.50.02 PM.png, Screen Shot 2016-05-01 at 3.51.01 PM.png, Screen Shot 2016-05-01 at 3.51.59 PM.png, Screen Shot 2016-05-01 at 3.55.30 PM.png
>
>
> History Server will load all tasks in a stage, which would cause memory leak if tasks occupy too many memory.
> In the following example, a single application would consume 1.1G memory of History Sever.
> I think we should limit tasks memory usages by adding spark.ui.retainedTasks.
--
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