ADH-8311: Fix Kerberized Solr audit writes on Java 25#52
Merged
Conversation
iamlapa
requested review from
Asmoday,
evgenii-tregubov,
pzindyaev and
tigrulya-exe
Asmoday
approved these changes
May 21, 2026
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.
Fix Kerberized Solr audit writes when Ranger runs with newer Java/Hadoop runtimes.
With Java 25 and Hadoop 3.4.3,
SubjectUtil.doAs()uses the newerSubject.callAs()path. The authenticatedSubjectis scoped to the current execution context and is not reliably available in SolrJ worker threads created byCloudSolrClientparallel updates.This caused Ranger audit writes to fail against Kerberized Solr with
401 Unauthorized/No valid credentials provided, even though the keytab login itself succeeded.Changes
CloudSolrClientinSolrAuditDestination.DbToSolrMigrationUtilfor audit migration writes to SolrCloud.Why
Ranger wraps
solrClient.add(...)in a Kerberos action, but SolrJ parallel updates can move the actual HTTP/SPNEGO update request to an internal executor thread. On modern Java/Hadoop, that thread does not inherit theSubjectfrom the caller context.Using
withParallelUpdates(false)keeps the Solr update request inside the active Kerberos action context.