[SPARK-57351][K8S][CORE] Enable spark.kubernetes.executor.useDriverPodIP by default#56412
Closed
dongjoon-hyun wants to merge 1 commit into
Closed
[SPARK-57351][K8S][CORE] Enable spark.kubernetes.executor.useDriverPodIP by default#56412dongjoon-hyun wants to merge 1 commit into
spark.kubernetes.executor.useDriverPodIP by default#56412dongjoon-hyun wants to merge 1 commit into
Conversation
Member
Author
|
Could you review this PR too, @viirya ? |
spark.kubernetes.executor.useDriverPodIP by defaultspark.kubernetes.executor.useDriverPodIP by default
spark.kubernetes.executor.useDriverPodIP by defaultspark.kubernetes.executor.useDriverPodIP by default
Member
Author
Member
Author
|
Could you review this PR too, @sarutak ? |
sarutak
approved these changes
Jun 9, 2026
viirya
approved these changes
Jun 9, 2026
Member
Author
dongjoon-hyun
added a commit
that referenced
this pull request
Jun 9, 2026
…odIP` by default ### What changes were proposed in this pull request? This PR sets the default value of `spark.kubernetes.executor.useDriverPodIP` to `true` at Apache Spark 4.3.0. ### Why are the changes needed? Introduced in SPARK-53944 (4.1.0), this option lets executor pods connect to the driver pod IP directly instead of the driver's Kubernetes `Service`, bypassing the known K8s DNS issue. Since a Spark driver pod is not restarted during an application, its IP is stable, making this a safe default that avoids DNS lookups. - #52650 ### Does this PR introduce _any_ user-facing change? Yes. By default, executor pods now connect to the driver via the driver pod IP instead of the driver `Service` DNS name. To restore the legacy behavior, set `spark.kubernetes.executor.useDriverPodIP` to `false`. ### How was this patch tested? Pass the CIs. ### Was this patch authored or co-authored using generative AI tooling? Generated-by: Claude Code (Opus 4.8) Closes #56412 from dongjoon-hyun/SPARK-57351. Authored-by: Dongjoon Hyun <dongjoon@apache.org> Signed-off-by: Dongjoon Hyun <dongjoon@apache.org> (cherry picked from commit 2bb8b20) Signed-off-by: Dongjoon Hyun <dongjoon@apache.org>
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?
This PR sets the default value of
spark.kubernetes.executor.useDriverPodIPtotrueat Apache Spark 4.3.0.Why are the changes needed?
Introduced in SPARK-53944 (4.1.0), this option lets executor pods connect to the driver pod IP directly instead of the driver's Kubernetes
Service, bypassing the known K8s DNS issue. Since a Spark driver pod is not restarted during an application, its IP is stable, making this a safe default that avoids DNS lookups.spark.kubernetes.executor.useDriverPodIP#52650Does this PR introduce any user-facing change?
Yes. By default, executor pods now connect to the driver via the driver pod IP instead of the driver
ServiceDNS name. To restore the legacy behavior, setspark.kubernetes.executor.useDriverPodIPtofalse.How was this patch tested?
Pass the CIs.
Was this patch authored or co-authored using generative AI tooling?
Generated-by: Claude Code (Opus 4.8)