You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Apache Spark (JIRA)" <ji...@apache.org> on 2016/03/04 23:20:40 UTC

[jira] [Assigned] (SPARK-13688) Add option to use dynamic allocation even if spark.executor.instances is set.

     [ https://issues.apache.org/jira/browse/SPARK-13688?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Apache Spark reassigned SPARK-13688:
------------------------------------

    Assignee: Apache Spark

> Add option to use dynamic allocation even if spark.executor.instances is set.
> -----------------------------------------------------------------------------
>
>                 Key: SPARK-13688
>                 URL: https://issues.apache.org/jira/browse/SPARK-13688
>             Project: Spark
>          Issue Type: Bug
>          Components: YARN
>    Affects Versions: 1.6.0
>            Reporter: Ryan Blue
>            Assignee: Apache Spark
>
> When both spark.dynamicAllocation.enabled and spark.executor.instances are set, dynamic resource allocation is disabled (see SPARK-9092). This is a reasonable default, but I think there should be a configuration property to override it because it isn't obvious to users that dynamic allocation and number of executors are mutually exclusive. We see users setting --num-executors because that looks like what they want: a way to get more executors.
> I propose adding a new boolean property, spark.dynamicAllocation.overrideNumExecutors, that makes dynamic allocation the default when both are set and uses --num-executors as the minimum number of executors.



--
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