You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Andrew Or (JIRA)" <ji...@apache.org> on 2015/08/07 19:34:45 UTC
[jira] [Updated] (SPARK-9731) Standalone scheduling incorrect cores
if spark.executor.cores is not set
[ https://issues.apache.org/jira/browse/SPARK-9731?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrew Or updated SPARK-9731:
-----------------------------
Priority: Blocker (was: Major)
> Standalone scheduling incorrect cores if spark.executor.cores is not set
> ------------------------------------------------------------------------
>
> Key: SPARK-9731
> URL: https://issues.apache.org/jira/browse/SPARK-9731
> Project: Spark
> Issue Type: Bug
> Components: Deploy
> Affects Versions: 1.5.0
> Reporter: Carson Wang
> Priority: Blocker
>
> The issue only happens if `spark.executor.cores` is not set and executor memory is set to a high value.
> For example, if we have a worker with 4G and 10 cores and we set `spark.executor.memory` to 3G, then only 1 core is assigned to the executor. The correct number should be 10 cores.
--
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