You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Hendra Saputra (Jira)" <ji...@apache.org> on 2023/09/25 09:20:00 UTC

[jira] [Comment Edited] (SPARK-45278) Make Yarn executor's bindAddress configurable

    [ https://issues.apache.org/jira/browse/SPARK-45278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17767932#comment-17767932 ] 

Hendra Saputra edited comment on SPARK-45278 at 9/25/23 9:19 AM:
-----------------------------------------------------------------

PR is up for review [https://github.com/apache/spark/pull/42870]

Thanks


was (Author: JIRAUSER302328):
PR is up for review [https://github.com/apache/spark/pull/42870.] Thanks

> Make Yarn executor's bindAddress configurable
> ---------------------------------------------
>
>                 Key: SPARK-45278
>                 URL: https://issues.apache.org/jira/browse/SPARK-45278
>             Project: Spark
>          Issue Type: Improvement
>          Components: Spark Core
>    Affects Versions: 3.5.0
>            Reporter: Hendra Saputra
>            Assignee: Nishchal Venkataramana
>            Priority: Major
>              Labels: pull-request-available
>
> An improvement has been made in SPARK-24203 that executor's bind address is configurable. Unfortunately this configuration hasn't implemented in Yarn.
> When Yarn cluster is deployed in in Kubernetes, it is preferable to bind the executor to loopback interface or all interface. This Jira is to allow Yarn to bind the executor to either pod IP or loopbak interface or all interface to allow mesh integration like Istio with the cluster.
> Another linked Jira explained *Allowing binding to all IPs* very well SPARK-42411 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org