You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Sean Owen (JIRA)" <ji...@apache.org> on 2015/05/25 09:12:17 UTC
[jira] [Updated] (SPARK-7699) Number of executors can be reduced
from initial before work is scheduled
[ https://issues.apache.org/jira/browse/SPARK-7699?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sean Owen updated SPARK-7699:
-----------------------------
Priority: Minor (was: Major)
Issue Type: Improvement (was: Bug)
Summary: Number of executors can be reduced from initial before work is scheduled (was: Config "spark.dynamicAllocation.initialExecutors" has no effect )
Should the allocation thread starts after the initial allocation is made then? I don't know how easy that is but it sounds more like the intended behavior. That seems better than yet another flag, another bit of arbitrary waiting. Anyway, if anything that's what this JIRA is about so I'm changing the title/status.
> Number of executors can be reduced from initial before work is scheduled
> ------------------------------------------------------------------------
>
> Key: SPARK-7699
> URL: https://issues.apache.org/jira/browse/SPARK-7699
> Project: Spark
> Issue Type: Improvement
> Components: Spark Core
> Reporter: meiyoula
> Priority: Minor
>
> spark.dynamicAllocation.minExecutors 2
> spark.dynamicAllocation.initialExecutors 3
> spark.dynamicAllocation.maxExecutors 4
> Just run the spark-shell with above configurations, the initial executor number is 2.
--
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