-
Notifications
You must be signed in to change notification settings - Fork 29.4k
[SPARK-59296][CORE][FOLLOWUP] Run OIDC UserCredentialManager in local mode for parity with HadoopDelegationTokenManager
#58737
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
sarutak
wants to merge
3
commits into
apache:master
Choose a base branch
from
sarutak:oidc-propagation/local-mode-parity
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
3 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
With the
isLocalguard removed, local mode now wires the provider into the driver's HadoopConfigurationhere, but credentials are acquired only later, inLocalSchedulerBackend.start()(via_taskScheduler.start()). Driver-side FS access that happens before that point inSparkContextinitialization sees an emptySparkEnv.userCredentials:setCheckpointDir(spark.checkpoint.dir) andaddFile(spark.files/spark.archives) throw, soSparkContextconstruction fails.addJar(spark.jars) swallows the error, so the jar is silently dropped and tasks later fail withClassNotFoundException.For example,
local[*]+spark.security.oidc.enabled=true+ the AWS provider +spark.checkpoint.dir=s3a://bucket/ckptstarted fine before this PR (default credential chain), but fails after it.This is the same limitation that already exists in cluster mode, but this PR extends it to local mode, and the new scaladoc ("points at credentials that are actually populated") is not accurate for this window. Could you document this, or make sure the resolution phase runs before these accesses in local mode?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've documented it rather than resolving earlier in local mode, since moving resolution up would
diverge local from cluster and break the selection-vs-resolution separation (resolution does I/O and
must stay late).