You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2025/07/09 13:15:00 UTC
[jira] [Updated] (SPARK-35677) Support dynamic executor range for dynamic allocation
[ https://issues.apache.org/jira/browse/SPARK-35677?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
ASF GitHub Bot updated SPARK-35677:
-----------------------------------
Labels: pull-request-available (was: )
> Support dynamic executor range for dynamic allocation
> -----------------------------------------------------
>
> Key: SPARK-35677
> URL: https://issues.apache.org/jira/browse/SPARK-35677
> Project: Spark
> Issue Type: Improvement
> Components: Spark Core, SQL
> Affects Versions: 3.2.0
> Reporter: Kent Yao 2
> Priority: Major
> Labels: pull-request-available
>
> Currently, Spark allows users to set scalability within a Spark application using dynamic allocation. spark.dynamicAllocation.minExecutors & spark.dynamicAllocation.maxExecutors are used for scaling up and down. Within an application,Spark tactfully use them to request executors from cluster manager according to the real-time workload. Once set, the range is fixed through the whole application lifecycle. This is not very convenient for long-running application when the range should be changeable for some cases, such as:
> 1. the cluster manager itself or the queue will scale up and down, which looks very likely to happen in modern cloud platforms
> 2. the application is long-running, but the timeliness, priority, e.t.c are not only determined by the workload with the application, but also by the traffic across the cluster manager or just different moments
> 3. e.t.c.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org