jzhuge commented on PR #51948: URL: https://github.com/apache/spark/pull/51948#issuecomment-3624932896
> It's unnecessary to set up `ActiveProcessorCount` for modern JDK when `java` process running in a container (e.g., docker, contianerd), see [JDK-8146115](https://bugs.openjdk.org/browse/JDK-8146115) for more details. But I agree that this can also apply to local and standalone deployment. There are 2 cases when it is still useful to set `ActiveProcessorCount` in k8s with modern JDK 1. Strictly reserve some resource for sidecars in a k8s pod. For example, the container is allocated with 4 cpus, JDK is expected to use 3 cpus, reserving 1 for sidecars. 2. JDK container awareness may not work with some custom cgroup paths. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
