[SPARK-50996][K8S] Increase spark.kubernetes.allocation.batch.size to 10
#49681
Conversation
This file contains 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
HyukjinKwon
approved these changes
Jan 27, 2025
|
Thank you, @HyukjinKwon ! Merged to master/4.0. |
dongjoon-hyun
added a commit
that referenced
this pull request
Jan 27, 2025
…to 10 ### What changes were proposed in this pull request? This PR aims to increase `spark.kubernetes.allocation.batch.size` to 10 from 5 in Apache Spark 4.0.0. ### Why are the changes needed? Since Apache Spark 2.3.0, Apache Spark uses `5` as the default value of executor allocation batch size for 8 years conservatively. - #19468 Given that the improvement of K8s hardware infrastructure for last 8 year, we had better use a bigger value, `10`, from Apache Spark 4.0.0 in 2025. Technically, when we request 1200 executor pod, - Batch Size `5` takes 4 minutes. - Batch Size `10` takes 2 minutes. ### Does this PR introduce _any_ user-facing change? Yes, the users will see faster Spark job resource allocation. The migration guide is updated correspondingly. ### How was this patch tested? Pass the CIs. ### Was this patch authored or co-authored using generative AI tooling? No. Closes #49681 from dongjoon-hyun/SPARK-50996. Authored-by: Dongjoon Hyun <[email protected]> Signed-off-by: Dongjoon Hyun <[email protected]> (cherry picked from commit 9da1cd0) Signed-off-by: Dongjoon Hyun <[email protected]>
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 aims to increase
spark.kubernetes.allocation.batch.sizeto 10 from 5 in Apache Spark 4.0.0.Why are the changes needed?
Since Apache Spark 2.3.0, Apache Spark uses
5as the default value of executor allocation batch size for 8 years conservatively.Given that the improvement of K8s hardware infrastructure for last 8 year, we had better use a bigger value,
10, from Apache Spark 4.0.0 in 2025.Technically, when we request 1200 executor pod,
5takes 4 minutes.10takes 2 minutes.Does this PR introduce any user-facing change?
Yes, the users will see faster Spark job resource allocation. The migration guide is updated correspondingly.
How was this patch tested?
Pass the CIs.
Was this patch authored or co-authored using generative AI tooling?
No.