[jira] [Commented] (SPARK-8414) Ensure ClosureCleaner actually triggers clean ups

["Josh Rosen (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/SPARK-8414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14645598#comment-14645598 ] 

Josh Rosen commented on SPARK-8414:
-----------------------------------

I think the title here should refer to ContextCleaner instead of ClosureCleaner (I always mix them up myself when speaking).

I think we should really aim to get this in for 1.5.0, so I'm going to bump this to critical. I may take a shot at it this week.

> Ensure ClosureCleaner actually triggers clean ups
> -------------------------------------------------
>
>                 Key: SPARK-8414
>                 URL: https://issues.apache.org/jira/browse/SPARK-8414
>             Project: Spark
>          Issue Type: Bug
>          Components: Spark Core
>    Affects Versions: 1.4.0
>            Reporter: Andrew Or
>            Assignee: Andrew Or
>
> Right now it cleans up old references only through natural GCs, which may not occur if the driver has infinite RAM. We should do a periodic GC to make sure that we actually do clean things up. Something like once per 30 minutes seems relatively inexpensive.



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