[SPARK-55757][CORE] Improve spark.task.cpus validation#54559
Closed
dongjoon-hyun wants to merge 1 commit intoapache:masterfrom
Closed
[SPARK-55757][CORE] Improve spark.task.cpus validation#54559dongjoon-hyun wants to merge 1 commit intoapache:masterfrom
spark.task.cpus validation#54559dongjoon-hyun wants to merge 1 commit intoapache:masterfrom
Conversation
pan3793
approved these changes
Feb 28, 2026
Member
Author
|
Thank you, @pan3793 . |
Member
Author
|
Also, FYI, cc @peter-toth |
peter-toth
approved these changes
Feb 28, 2026
Member
Author
|
Thank you, @peter-toth ! Merged to master. |
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
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.
What changes were proposed in this pull request?
This PR aim to improve
spark.task.cpusvalidation.Why are the changes needed?
Currently, Apache Spark throws
java.lang.ArithmeticExceptionfor the invalidspark.task.cpus. We had better provide actionable direction.BEFORE
AFTER
Does this PR introduce any user-facing change?
This only changes the error message before starting Spark job.
How was this patch tested?
Pass the CIs with newly added test case.
Was this patch authored or co-authored using generative AI tooling?
Generated-by:
Gemini 3.1 Pro (High)onAntigravity.