[
https://issues.apache.org/jira/browse/YARN-7935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16543727#comment-16543727
]
Suma Shivaprasad commented on YARN-7935:
----------------------------------------
Attached patch for jenkins check which fixes review comments from Jason and
Erik with the following changes
1. For "host" networking mode in DockerLinuxContainerRuntime, the
CONTAINER_HOSTNAME env is set to the hostname in NM_HOST env which basically
derives it from nodemanager.address if set . This behaviour is the same for
DefaultContainerExecutor, other runtimes in LinuxContainerExecutor.
2. For other network modes in DockerLinuxContainerRuntime, it is set to the
yarn generated container host name
> Expose container's hostname to applications running within the docker
> container
> -------------------------------------------------------------------------------
>
> Key: YARN-7935
> URL: https://issues.apache.org/jira/browse/YARN-7935
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: yarn
> Reporter: Suma Shivaprasad
> Assignee: Suma Shivaprasad
> Priority: Major
> Labels: Docker
> Attachments: YARN-7935.1.patch, YARN-7935.2.patch, YARN-7935.3.patch,
> YARN-7935.4.patch
>
>
> Some applications have a need to bind to the container's hostname (like
> Spark) which is different from the NodeManager's hostname(NM_HOST which is
> available as an env during container launch) when launched through Docker
> runtime. The container's hostname can be exposed to applications via an env
> CONTAINER_HOSTNAME. Another potential candidate is the container's IP but
> this can be addressed in a separate jira.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
