[SPARK-52509][K8S] Cleanup shuffles from fallback storage #51199
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?
Shuffle data of individual shuffles are deleted from the fallback storage during regular shuffle cleanup.
Why are the changes needed?
Currently, the shuffle data are only removed from the fallback storage on Spark context shutdown. Long running Spark jobs accumulate shuffle data, though this data is not used by Spark any more. Those shuffles should be cleaned up while Spark context is running.
Does this PR introduce any user-facing change?
No
How was this patch tested?
Unit tests and manual test via reproduction example.
Run the reproduction example without the
<<< "$scala"
. In the Spark shell, execute this code:This writes some data of shuffle 0 to the fallback storage.
Invoking
System.gc()
removes that shuffle directory from the fallback storage. Exiting the Spark shell removes the whole application directory.Was this patch authored or co-authored using generative AI tooling?
No.