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 2016/02/29 23:40:18 UTC

[jira] [Updated] (SPARK-12817) Remove CacheManager and replace it with new BlockManager.getOrElseUpdate method

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

Josh Rosen updated SPARK-12817:
-------------------------------
    Summary: Remove CacheManager and replace it with new BlockManager.getOrElseUpdate method  (was: Simplify CacheManager code and remove unused BlockManager methods)

> Remove CacheManager and replace it with new BlockManager.getOrElseUpdate method
> -------------------------------------------------------------------------------
>
>                 Key: SPARK-12817
>                 URL: https://issues.apache.org/jira/browse/SPARK-12817
>             Project: Spark
>          Issue Type: Improvement
>          Components: Block Manager
>            Reporter: Josh Rosen
>            Assignee: Josh Rosen
>
> CacheManager directly calls MemoryStore.unrollSafely() and has its own logic for handling graceful fallback to disk when cached data does not fit in memory. However, this logic also exists inside of the MemoryStore itself, so this appears to be unnecessary duplication.
> We can remove this duplication and delete a significant amount of BlockManager code which existed only to support this CacheManager code.



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