You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Hyukjin Kwon (JIRA)" <ji...@apache.org> on 2019/05/21 03:59:21 UTC
[jira] [Updated] (SPARK-22567) spark.mesos.executor.memoryOverhead
equivalent for the Driver when running on Mesos
[ https://issues.apache.org/jira/browse/SPARK-22567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hyukjin Kwon updated SPARK-22567:
---------------------------------
Labels: bulk-closed (was: )
> spark.mesos.executor.memoryOverhead equivalent for the Driver when running on Mesos
> -----------------------------------------------------------------------------------
>
> Key: SPARK-22567
> URL: https://issues.apache.org/jira/browse/SPARK-22567
> Project: Spark
> Issue Type: Improvement
> Components: Mesos
> Affects Versions: 2.2.0
> Reporter: Michael Moss
> Priority: Minor
> Labels: bulk-closed
>
> spark.mesos.executor.memoryOverhead is:
> "The amount of additional memory, specified in MB, to be allocated per executor. By default, the overhead will be larger of either 384 or 10% of spark.executor.memory"
> It is important for every JVM process to have memory available to it, beyond its heap (Xmx) for native allocations.
> When using the MesosClusterDispatcher and running the Driver on Mesos (https://spark.apache.org/docs/latest/running-on-mesos.html#cluster-mode), it appears that the Driver's mesos sandbox is allocated with the same amount of memory (configured with spark.driver.memory) as the heap (Xmx) itself. This increases the prevalence of OOM exceptions.
--
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