[SPARK-49984][CORE] Fix duplicate JVM options #48488
Open
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?
Fix how the JVM options are supplemented with Java module options and IPv6 options. Get and set based on the exact value of
spark.*.extraJavaOptions
, and don't use the helper config which combines both default and extra Java options.Why are the changes needed?
The current approach using
DRIVER_JAVA_OPTIONS
andEXECUTOR_JAVA_OPTIONS
loads both thespark.*.extraJavaOptions
andspark.*.defaultJavaOptions
, adds the "supplemental" options, and then resaves the result inspark.*.extraJavaOptions
. This is because DRIVER_JAVA_OPTIONS is a config like:The result is
spark.*.defaultJavaOptions
being added multiple times tospark.*.extraJavaOptions
, and when the full options are actually pulled to launch a process, three copies of what was in thespark.*.defaultJavaOptions
ends up being included on the command line.Does this PR introduce any user-facing change?
No.
How was this patch tested?
Manual testing
Before:
After:
Was this patch authored or co-authored using generative AI tooling?
No