Account for PySpark memory in cluster resource requests - #2137
Merged
Merged
Conversation
Signed-off-by: Partho Sarthi <psarthi@nvidia.com>
Signed-off-by: Partho Sarthi <psarthi@nvidia.com>
Signed-off-by: Partho Sarthi <psarthi@nvidia.com>
Signed-off-by: Partho Sarthi <psarthi@nvidia.com>
SurajAralihalli
approved these changes
Sep 3, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
When AutoTuner recommends a positive
spark.executor.pyspark.memory, it now also recommends the setting Spark needs to include that memory in the executor resource request:spark.yarn.isPython=truespark.kubernetes.resource.type=pythonOnly the setting for the detected cluster manager is emitted. Standalone, local, and unknown masters are unchanged.
The PySpark memory rebalance also checks that the accounting setting can be applied. If it is excluded or enforced to an incompatible value, the rebalance is skipped instead of producing a partially valid memory layout.
Fixes #2134.
Testing
mvn verify(836 tests passed; Scalastyle reported no errors or warnings)