You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Weichen Xu (JIRA)" <ji...@apache.org> on 2016/07/24 13:30:20 UTC
[jira] [Updated] (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 ]
Weichen Xu updated SPARK-16696:
-------------------------------
Description:
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.
was:
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, LDA, Word2Vec, has this problem. Several places unused broadcast vars even neither call unpersit() nor call destroy()
> 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: Bug
> Components: ML, MLlib
> Affects Versions: 2.0.1, 2.1.0
> Reporter: Weichen Xu
> 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