GitHub user rdblue opened a pull request:

    https://github.com/apache/spark/pull/11528

    SPARK-13688: Add spark.dynamicAllocation.overrideNumInstances.

    When both the number of executor instances and dynamic allocation are 
configured, dynamic allocation is ignored and the number of executors is 
statically set. This introduces a configuration property to change this 
behavior so that cluster administrators can make dynamic allocation the default 
when users set `--num-executors` instead of 
`spark.dynamicAllocation.minExecutors` and unintentionally disable dynamic 
allocation for a job.
    
    This includes unit tests for the new cases and updates to documentation.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/rdblue/spark 
SPARK-13688-override-num-instances

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/spark/pull/11528.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #11528
    
----
commit e79fe20dee37946a188e1b86578fa1f0872b39e6
Author: Ryan Blue <[email protected]>
Date:   2016-03-04T21:44:13Z

    SPARK-13688: Add spark.dynamicAllocation.overrideNumInstances.
    
    When both the number of executor instances and dynamic allocation are
    configured, dynamic allocation is ignored and the number of executors is
    statically set. This introduces a configuration property to change this
    behavior so that cluster administrators can make dynamic allocation the
    default when users set --num-executors instead of
    spark.dynamicAllocation.minExecutors and unintentionally disable dynamic
    allocation for a job.

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to