You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "David C Navas (JIRA)" <ji...@apache.org> on 2019/05/21 18:11:00 UTC
[jira] [Resolved] (SPARK-27727) Asynchronous ElementStore cleanup
should have only one pending cleanup per class
[ https://issues.apache.org/jira/browse/SPARK-27727?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
David C Navas resolved SPARK-27727.
-----------------------------------
Resolution: Duplicate
Fix Version/s: 3.0.0
> Asynchronous ElementStore cleanup should have only one pending cleanup per class
> --------------------------------------------------------------------------------
>
> Key: SPARK-27727
> URL: https://issues.apache.org/jira/browse/SPARK-27727
> Project: Spark
> Issue Type: Sub-task
> Components: Spark Core
> Affects Versions: 2.3.3
> Reporter: David C Navas
> Priority: Major
> Fix For: 3.0.0
>
> Attachments: AsyncDefer.pdf
>
>
> If ElementTrackingStore cleanup work takes too long to run, the asynchronous requests to run the cleanup can backup in the executor. Although eventually these requests will do nothing (or very little), they are a potential source of semi-permanent memory use/leaks.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org