You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Xiangrui Meng (JIRA)" <ji...@apache.org> on 2018/08/29 14:14:00 UTC
[jira] [Resolved] (SPARK-25266) Fix memory leak in Barrier
Execution Mode
[ https://issues.apache.org/jira/browse/SPARK-25266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Xiangrui Meng resolved SPARK-25266.
-----------------------------------
Resolution: Fixed
Fix Version/s: 2.4.0
Issue resolved by pull request 22258
[https://github.com/apache/spark/pull/22258]
> Fix memory leak in Barrier Execution Mode
> -----------------------------------------
>
> Key: SPARK-25266
> URL: https://issues.apache.org/jira/browse/SPARK-25266
> Project: Spark
> Issue Type: Bug
> Components: Scheduler, Spark Core
> Affects Versions: 2.4.0
> Reporter: Kousuke Saruta
> Assignee: Kousuke Saruta
> Priority: Critical
> Fix For: 2.4.0
>
>
> BarrierCoordinator uses Timer and TimerTask. `TimerTask#cancel()` is invoked in ContextBarrierState#cancelTimerTask but `Timer#purge()` is never invoked.
> Once a TimerTask is scheduled, the reference to it is not released until `Timer#purge()` is invoked even though `TimerTask#cancel()` is invoked.
>
--
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