You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Apache Spark (JIRA)" <ji...@apache.org> on 2015/12/07 05:11:10 UTC
[jira] [Commented] (SPARK-12165) Execution memory requests may fail
to evict storage blocks if storage memory usage is below max memory
[ https://issues.apache.org/jira/browse/SPARK-12165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15044342#comment-15044342 ]
Apache Spark commented on SPARK-12165:
--------------------------------------
User 'JoshRosen' has created a pull request for this issue:
https://github.com/apache/spark/pull/10170
> Execution memory requests may fail to evict storage blocks if storage memory usage is below max memory
> ------------------------------------------------------------------------------------------------------
>
> Key: SPARK-12165
> URL: https://issues.apache.org/jira/browse/SPARK-12165
> Project: Spark
> Issue Type: Bug
> Components: Spark Core
> Reporter: Josh Rosen
> Assignee: Josh Rosen
> Priority: Blocker
>
> Consider a scenario where storage memory usage has grown past the size of the unevictable storage region ({{spark.memory.storageFraction}} * maxMemory) and a task needs to acquire more execution memory by reclaiming evictable storage memory. If the storage memory usage is less than maxMemory, then there's a possibility that no storage blocks will be evicted. This is caused by how {{MemoryStore.ensureFreeSpace()}} is called inside of {{StorageMemoryPool.shrinkPoolToReclaimSpace()}}.
> Here's a failing regression test which demonstrates this bug: https://github.com/apache/spark/commit/b519fe628a9a2b8238dfedbfd9b74bdd2ddc0de4?diff=unified#diff-b3a7cd2e011e048908d70f743c0ed7cfR155
--
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