[SPARK-46912][CORE] Using correct environment variables on workers of StandAlone cluster #51314
+43
−7
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 changes were proposed in this pull request?
Fixing environment for stand alone cluster when launching driver/executor processes.
Why are the changes needed?
Fixing a bug when submitting to a standalone cluster from a machine which has different envs and paths
Does this PR introduce any user-facing change?
Yes. According to https://issues.apache.org/jira/browse/SPARK-46912 when submitting to stand alone cluster in cluster mode, driver was trying to launch java on the path from JAVA_HOME, which, in turn, was taken from "submitter" machine not from the worker one. And java.IOException with "Cannot run program /${wrongPath}" is thrown.
How was this patch tested?
Unit tests.
Submitting to upgraded custom SA cluster from a docker container which has a different environment than cluster.
Was this patch authored or co-authored using generative AI tooling?
No