[LIVY-1063] Fix resource leak in Kubernetes service account token refresh - #536
Open
nileshrathi345 wants to merge 1 commit into
Open
[LIVY-1063] Fix resource leak in Kubernetes service account token refresh#536nileshrathi345 wants to merge 1 commit into
nileshrathi345 wants to merge 1 commit into
Conversation
Contributor
Author
gyogal
approved these changes
Aug 4, 2026
gyogal
left a comment
gyogal
left a comment
Contributor
There was a problem hiding this comment.
LGTM, thanks @nileshrathi345 !
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
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?
Reuse the existing
KubernetesClientduring service account token refresh instead ofrecreating
DefaultKubernetesClientevery 5 minutes without closing the old client.JIRA: https://issues.apache.org/jira/browse/LIVY-1063
How was this patch tested?
mvn -pl server -am -DskipITs testconfig.setOauthToken(); no new client creationverified "Refreshed Kubernetes service account token." logs every ~5 minutes and
native/HTTP client thread count remains stable over several refresh cycles
Was this patch authored or co-authored using generative AI tooling?
No