[SPARK-53906][K8S] Protect ExecutorPodsAllocator.numOutstandingPods as protected val
#52614
Conversation
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
… as `protected val`
|
cc @peter-toth |
peter-toth
approved these changes
Oct 14, 2025
|
Thank you so much, @peter-toth . |
|
Merged to master for Apache Spark 4.1.0-preview3. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
What changes were proposed in this pull request?
This PR aims to protect
ExecutorPodsAllocator.numOutstandingPodsasprotected val.Why are the changes needed?
We had better protect this properly instead of commenting it.
spark/resource-managers/kubernetes/core/src/main/scala/org/apache/spark/scheduler/cluster/k8s/ExecutorPodsAllocator.scala
Lines 108 to 109 in ff0f1ab
Does this PR introduce any user-facing change?
No. This is not supposed to be used internally.
How was this patch tested?
Pass the CIs.
Was this patch authored or co-authored using generative AI tooling?
No.