[SPARK-23719] Use correct hostname in non-host networking mode in hadoop 3 docker support

• Type: Improvement
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 3.1.0
• Component/s: Spark Core, YARN
• Assignee: Unassigned
• Reporter: Mridul Muralidharan
• Created: 17/Mar/18 02:03
• Updated: 16/Mar/20 22:55

Description

Hostname (node-id's hostname field) specified by RM in allocated containers is the NM_HOST and not the hostname which will be used by the container when running in docker container executor : the actual container hostname is generated at runtime.

Due to this spark executor's are unable to launch in non-host networking mode when leveraging docker support in hadoop 3 - due to bind failures as hostname they are trying to bind to is of the host machine and not the container.

We can leverage YARN-7935 to fetch the container's hostname (when available) else fallback to existing mechanism - when running executors.

Issue Links

• blocks: SPARK-23717 Leverage docker support in Hadoop 3
• blocks: SPARK-23720 Leverage shuffle service when running in non-host networking mode in hadoop 3 docker support
• relates to: YARN-7935 Expose container's hostname to applications running within the docker container