[fix][COM][hadoop-common] resolve kerberos tgt expiry issue for cached hdfs filesystem - #1093
Merged
Merged
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
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 is the purpose of the change
Background/Problem:
When the HDFS FileSystem cache is enabled in a Kerberos-secured cluster, the cached FileSystem holds a Kerberos TGT that can expire over time. Once expired, reusing the cached FileSystem leads to Kerberos authentication errors, because the cache returns the stale FileSystem without checking TGT validity.
Purpose of Change:
To address this problem, this PR adds a feature switch
linkis.hadoop.hdfs.tgt.proactive.check.enable(default off). When enabled, before returning a cached FileSystem the code checks the UGI's TGT validity via a newKerberosTgtUtils; if the TGT has expired, the stale cached container is removed and a new FileSystem with a fresh TGT is created.Value/Impact:
After the change, cached HDFS FileSystems are no longer reused once their Kerberos TGT expires, eliminating authentication failures in long-running cached scenarios. The switch defaults to off, so existing behavior is unchanged when disabled.
Related issues/PRs
Related issues: close #1092
Related pr:none
Brief change log
linkis.hadoop.hdfs.tgt.proactive.check.enableswitch in HadoopConfChecklist