[SPARK-56028][CORE] Fix shuffle block GC not cleanup checksum file#54857
Open
CavemanIV wants to merge 2 commits intoapache:masterfrom
Open
[SPARK-56028][CORE] Fix shuffle block GC not cleanup checksum file#54857CavemanIV wants to merge 2 commits intoapache:masterfrom
CavemanIV wants to merge 2 commits intoapache:masterfrom
Conversation
LuciferYang
changed the title
CavemanIV
changed the title
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
1 participant
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?
Followup SPARK-37618
When periodical cleanup triggers on executor block files GC, delete checksum files as well
Why are the changes needed?
Helps reduce small files on executor when dynamic executor allocation is enabled. As shuffle related .data and .index are deleted already, no need to keep .checksum
Does this PR introduce any user-facing change?
No
How was this patch tested?
Manually test on internal cluster
Was this patch authored or co-authored using generative AI tooling?
No