[
https://issues.apache.org/jira/browse/YARN-8675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16588998#comment-16588998
]
Billie Rinaldi commented on YARN-8675:
--------------------------------------
Perhaps we should always set the hostname when the AM has provided one through
the YARN_CONTAINER_RUNTIME_DOCKER_CONTAINER_HOSTNAME env var, but place
conditions on when the DockerLinuxContainerRuntime makes up a default hostname
to set. We could remove the default hostname entirely, or just set it when net
!= host.
Another probably ill-advised option would be to have the runtime populate the
registry when the runtime sets a default hostname and RegistryDNS is enabled.
But then we'd have to figure out a way to clean up the registry later.
> Setting hostname of docker container breaks with "host" networking mode for
> Apps which do not run as a YARN service
> -------------------------------------------------------------------------------------------------------------------
>
> Key: YARN-8675
> URL: https://issues.apache.org/jira/browse/YARN-8675
> Project: Hadoop YARN
> Issue Type: Bug
> Reporter: Yesha Vora
> Assignee: Suma Shivaprasad
> Priority: Major
> Labels: Docker
>
> Applications like the Spark AM currently do not run as a YARN service and
> setting hostname breaks driver/executor communication if docker version
> >=1.13.1 , especially with wire-encryption turned on.
> YARN-8027 sets the hostname if YARN DNS is enabled. But the cluster could
> have a mix of YARN service/native Applications.
> The proposal is to not set the hostname when "host" networking mode is
> enabled.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
