[
https://issues.apache.org/jira/browse/SPARK-53209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John Zhuge updated SPARK-53209:
-------------------------------
Summary: Add ActiveProcessorCount JVM option to YARN executor and AM
(was: Add ActiveProcessorCount JVM option to Spark driver and executor in YARN
mode)
> Add ActiveProcessorCount JVM option to YARN executor and AM
> ------------------------------------------------------------
>
> Key: SPARK-53209
> URL: https://issues.apache.org/jira/browse/SPARK-53209
> Project: Spark
> Issue Type: Bug
> Components: Spark Core, YARN
> Affects Versions: 2.4.5
> Reporter: John Zhuge
> Priority: Major
> Labels: pull-request-available
>
> When starting Spark driver and executors on Yarn cluster, the JVM process can
> discover all CPU cores on the system and set thread-pool or GC threads based
> on that value. We should limit what the JVM sees for the number of cores set
> by the user (spark.driver.cores or spark.executor.cores) by
> "-XX:ActiveProcessorCount", which was introduced in Java 8u191.
> Especially in running Spark on Yarn inside Kubernetes container, the number
> of CPU cores discovered sometimes is 1, which means it always use 1 thread in
> the default thread pool, or GC threads.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
