You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Sean Owen (JIRA)" <ji...@apache.org> on 2016/07/30 15:08:20 UTC

[jira] [Resolved] (SPARK-16696) unused broadcast variables should call destroy instead of unpersist

     [ https://issues.apache.org/jira/browse/SPARK-16696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sean Owen resolved SPARK-16696.
-------------------------------
       Resolution: Fixed
    Fix Version/s: 2.1.0

Issue resolved by pull request 14333
[https://github.com/apache/spark/pull/14333]

> unused broadcast variables should call destroy instead of unpersist
> -------------------------------------------------------------------
>
>                 Key: SPARK-16696
>                 URL: https://issues.apache.org/jira/browse/SPARK-16696
>             Project: Spark
>          Issue Type: Improvement
>          Components: ML, MLlib
>    Affects Versions: 2.0.1
>            Reporter: Weichen Xu
>             Fix For: 2.1.0
>
>   Original Estimate: 1m
>  Remaining Estimate: 1m
>
> Unused broadcast variables should call destroy() instead of unpersist() so that the memory can released in time, even in driver-side.
> currently, several algorithm in ML, such as KMeans, Word2Vec, has this problem.



--
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