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 2014/12/10 07:49:13 UTC
[jira] [Commented] (SPARK-3918) Forget Unpersist in
RandomForest.scala(train Method)
[ https://issues.apache.org/jira/browse/SPARK-3918?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14240732#comment-14240732 ]
Sean Owen commented on SPARK-3918:
----------------------------------
[~josephkb] The PR you opened for this an another issue was merged, and notes indicate it should remove an unpersist call, but I didn't see that in the change? https://github.com/apache/spark/pull/2785/files
Is this just obsoleted or was the change not in the PR actually?
> Forget Unpersist in RandomForest.scala(train Method)
> ----------------------------------------------------
>
> Key: SPARK-3918
> URL: https://issues.apache.org/jira/browse/SPARK-3918
> Project: Spark
> Issue Type: Bug
> Components: MLlib
> Affects Versions: 1.2.0
> Environment: All
> Reporter: junlong
> Assignee: Joseph K. Bradley
> Labels: decisiontree, train, unpersist
> Fix For: 1.1.0
>
> Original Estimate: 10m
> Remaining Estimate: 10m
>
> In version 1.1.0 DecisionTree.scala, train Method, treeInput has been persisted in Memory, but without unpersist. It caused heavy DISK usage.
> In github version(1.2.0 maybe), RandomForest.scala, train Method, baggedInput has been persisted but without unpersisted too.
--
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