You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Dongjoon Hyun (Jira)" <ji...@apache.org> on 2020/03/16 22:54:06 UTC

[jira] [Updated] (SPARK-23720) Leverage shuffle service when running in non-host networking mode in hadoop 3 docker support

     [ https://issues.apache.org/jira/browse/SPARK-23720?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dongjoon Hyun updated SPARK-23720:
----------------------------------
    Affects Version/s:     (was: 3.0.0)
                       3.1.0

> Leverage shuffle service when running in non-host networking mode in hadoop 3 docker support
> --------------------------------------------------------------------------------------------
>
>                 Key: SPARK-23720
>                 URL: https://issues.apache.org/jira/browse/SPARK-23720
>             Project: Spark
>          Issue Type: Improvement
>          Components: Spark Core
>    Affects Versions: 3.1.0
>            Reporter: Mridul Muralidharan
>            Priority: Major
>
> In current external shuffle service integration, hostname of the executor and the shuffle service is the same while the port's are different (shuffle service port vs block manager port).
> When running in non-host networking mode under docker, in yarn, the shuffle service runs on the NM_HOST while the docker container run's under its own (ephemeral and generated) hostname.
> We should make use of the container's host machine's hostname for shuffle service and not the container hostname, when external shuffle is enabled.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

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