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 2026/03/12 06:15:00 UTC

[jira] [Updated] (SPARK-55970) Cap spark.executor.cores to max worker cores when it's set too large

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

ASF GitHub Bot updated SPARK-55970:
-----------------------------------
    Labels: pull-request-available  (was: )

> Cap spark.executor.cores to max worker cores when it's set too large
> --------------------------------------------------------------------
>
>                 Key: SPARK-55970
>                 URL: https://issues.apache.org/jira/browse/SPARK-55970
>             Project: Spark
>          Issue Type: Improvement
>          Components: Spark Core
>    Affects Versions: 4.2.0
>            Reporter: wuyi
>            Priority: Major
>              Labels: pull-request-available
>
> Users may mistakenly set a wrong spark.executor.cores, which is large than any of available core in all workers. And they'd be confused and complain where there is no executor launched. This ticket proposes to automactillay cap the wrong setting to the max available cores of all the workers so that executor is able to launch.



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