You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@spark.apache.org by "Josh Rosen (JIRA)" <ji...@apache.org> on 2015/07/29 09:14:04 UTC

[jira] [Updated] (SPARK-8414) Ensure ContextCleaner actually triggers clean ups

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

Josh Rosen updated SPARK-8414:
------------------------------
    Summary: Ensure ContextCleaner actually triggers clean ups  (was: Ensure ClosureCleaner actually triggers clean ups)

> Ensure ContextCleaner 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
>            Priority: Critical
>
> 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