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/06/01 13:21:00 UTC
[jira] [Resolved] (SPARK-27811) Docs of
spark.driver.memoryOverhead and spark.executor.memoryOverhead exists a
little ambiguity
[ https://issues.apache.org/jira/browse/SPARK-27811?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sean Owen resolved SPARK-27811.
-------------------------------
Resolution: Fixed
Fix Version/s: 3.0.0
Issue resolved by pull request 24671
[https://github.com/apache/spark/pull/24671]
> Docs of spark.driver.memoryOverhead and spark.executor.memoryOverhead exists a little ambiguity
> ------------------------------------------------------------------------------------------------
>
> Key: SPARK-27811
> URL: https://issues.apache.org/jira/browse/SPARK-27811
> Project: Spark
> Issue Type: Improvement
> Components: Documentation, Spark Core
> Affects Versions: 2.3.0, 2.4.0
> Reporter: jiaan.geng
> Assignee: jiaan.geng
> Priority: Trivial
> Fix For: 3.0.0
>
>
> I found the docs of {{spark.driver.memoryOverhead}} and {{spark.executor.memoryOverhead}} exists a little ambiguity.
> For example, the origin docs of {{spark.driver.memoryOverhead}} start with {{The amount of off-heap memory to be allocated per driver in cluster mode}}.
> But {{MemoryManager}} also managed a memory area named off-heap used to allocate memory in tungsten mode.
> So I think the description of {{spark.driver.memoryOverhead}} always make confused.
> {{spark.executor.memoryOverhead}} has the same confused with {{spark.driver.memoryOverhead}}.
--
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