You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Cheng Lian (JIRA)" <ji...@apache.org> on 2015/07/27 07:43:04 UTC
[jira] [Reopened] (SPARK-9353) Standalone scheduling memory
requirement incorrect if cores per executor is not set
[ https://issues.apache.org/jira/browse/SPARK-9353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Cheng Lian reopened SPARK-9353:
-------------------------------
Reopening this issue because [PR #7686|https://github.com/apache/spark/pull/7686] is reverted for 1.4.
> Standalone scheduling memory requirement incorrect if cores per executor is not set
> -----------------------------------------------------------------------------------
>
> Key: SPARK-9353
> URL: https://issues.apache.org/jira/browse/SPARK-9353
> Project: Spark
> Issue Type: Bug
> Components: Deploy
> Affects Versions: 1.5.0
> Reporter: Andrew Or
> Assignee: Andrew Or
> Fix For: 1.5.0
>
>
> I tried to come up with a more succinct title.
> The issue only happens if `spark.executor.cores` is not set. Right now if we have a worker with 8G, and we set `spark.executor.memory` to 1G, then the executor launched on the worker can have at most 8 cores, even if the worker has more cores available.
> This is caused by the fix in SPARK-8881.
--
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