[
https://issues.apache.org/jira/browse/YARN-7935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16416215#comment-16416215
]
Suma Shivaprasad commented on YARN-7935:
----------------------------------------
[~eyang]
In docker user defined networks including overlays/user defined bridges, like I
mentioned in my earlier comment
https://issues.apache.org/jira/browse/YARN-7935?focusedCommentId=16414269&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16414269,
the hostname to IP resolution would happen through docker embedded DNS.
YARN-7994 would set up the necessary network alias which is set to the Yarn
generated container's hostname(same as what is set in CONTAINER_HOSTNAME) in
docker embedded DNS for this resolution to work.
In "host" mode , CONTAINER_HOSTNAME = NM's host name which is already routable.
> 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
> Attachments: YARN-7935.1.patch, YARN-7935.2.patch, YARN-7935.3.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]
