[SPARK-41540][K8S] Add DISK_USED executor roll policy
#39083
Closed
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
HyukjinKwon
approved these changes
Dec 16, 2022
Member
Author
|
Oh, thank you for review, @HyukjinKwon . |
Member
Author
|
Also, cc @viirya . |
viirya
approved these changes
Dec 16, 2022
Member
viirya
left a comment
viirya
left a comment
There was a problem hiding this comment.
Looks good to me. We may need to update docs/running-on-kubernetes.md too.
Member
Author
|
Thank you, @HyukjinKwon and @viirya . Yes, we need to revise the doc too. |
Member
Author
|
All tests passed. Merged to master. |
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.
What changes were proposed in this pull request?
This PR aims to add a new executor roll policy,
DISK_USED, which chooses the executor whose used disk size is biggest.Why are the changes needed?
To provide a new built-in policy to the users.
Does this PR introduce any user-facing change?
No. This is a new policy.
How was this patch tested?
Pass the CIs.