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 2019/01/26 04:29:00 UTC
[jira] [Resolved] (SPARK-26698) Use ConfigEntry for hardcoded
configs for memory and storage categories
[ https://issues.apache.org/jira/browse/SPARK-26698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sean Owen resolved SPARK-26698.
-------------------------------
Resolution: Fixed
Fix Version/s: 3.0.0
Issue resolved by pull request 23623
[https://github.com/apache/spark/pull/23623]
> Use ConfigEntry for hardcoded configs for memory and storage categories
> -----------------------------------------------------------------------
>
> Key: SPARK-26698
> URL: https://issues.apache.org/jira/browse/SPARK-26698
> Project: Spark
> Issue Type: Improvement
> Components: Spark Core
> Affects Versions: 3.0.0
> Reporter: SongYadong
> Assignee: SongYadong
> Priority: Major
> Fix For: 3.0.0
>
> Original Estimate: 48h
> Remaining Estimate: 48h
>
> Some of following memory and storage related configs are still hardcoded, We try to use ConfigEntry and put them in the config package :
> spark.storage.cleanupFilesAfterExecutorExit
> spark.diskStore.subDirectories
> spark.block.failures.beforeLocationRefresh
> spark.storage.unrollMemoryThreshold
> spark.storage.memoryMapThreshold
> spark.memory.storageFraction
> spark.memory.offHeap.enabled
> spark.memory.offHeap.size
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org