Skip to content

Conversation

@lukmajercak
Copy link

What changes were proposed in this pull request?

Adding spark.executor.bindAddress to allow overriding the address to which the RPC server will bind to on each executor.

How was this patch tested?

Have been running a private build with this in our production cluster for a while.

@lukmajercak lukmajercak changed the title Add spark.executor.bindAddress [SPARK-24203] Add spark.executor.bindAddress May 7, 2018
@lukmajercak lukmajercak changed the title [SPARK-24203] Add spark.executor.bindAddress [SPARK-24203][core] Add spark.executor.bindAddress May 7, 2018
@vanzin
Copy link
Contributor

vanzin commented Jun 4, 2018

How does this work when you have more than one executor?

@AmplabJenkins
Copy link

Can one of the admins verify this patch?

@HyukjinKwon
Copy link
Member

ping @lukmajercak for @vanzin's comment

@asfgit asfgit closed this in 1a4fda8 Jul 19, 2018
dbtsai pushed a commit that referenced this pull request Nov 13, 2019
### What changes were proposed in this pull request?
With this change, executor's bindAddress is passed as an input parameter for RPCEnv.create.
A previous PR #21261 which addressed the same, was using a Spark Conf property to get the bindAddress which wouldn't have worked for multiple executors.
This PR is to enable anyone overriding CoarseGrainedExecutorBackend with their custom one to be able to invoke CoarseGrainedExecutorBackend.main() along with the option to configure bindAddress.

### Why are the changes needed?
This is required when Kernel-based Virtual Machine (KVM)'s are used inside Linux container where the hostname is not the same as container hostname.

### Does this PR introduce any user-facing change?
No

### How was this patch tested?
Tested by running jobs with executors on KVMs inside a linux container.

Closes #26331 from nishchalv/SPARK-29670.

Lead-authored-by: Nishchal Venkataramana <[email protected]>
Co-authored-by: nishchal <[email protected]>
Signed-off-by: DB Tsai <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants