[SPARK-58438][CORE] Close FileSystem cache after token renewal - #58110
Open
MrHappyEnding wants to merge 1 commit into
Open
[SPARK-58438][CORE] Close FileSystem cache after token renewal#58110MrHappyEnding wants to merge 1 commit into
MrHappyEnding wants to merge 1 commit into
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
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?
Close FileSystem instances cached for the fresh Hadoop UGI after obtaining delegation tokens. The cleanup is shared by both one-time token acquisition and scheduled renewal, and runs in a
finallyblock.A regression test was added to verify that FileSystem instances created during renewal are closed.
Why are the changes needed?
Each renewal creates a fresh UGI. FileSystem instances cached for that UGI were not closed by the renewal path, causing the Hadoop FileSystem cache to grow after every renewal.
Does this PR introduce any user-facing change?
No.
How was this patch tested?
Ran:
Was this patch authored or co-authored using generative AI tooling?
Generated-by: Codex