[
https://issues.apache.org/jira/browse/YARN-7935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16372320#comment-16372320
]
Mridul Muralidharan commented on YARN-7935:
-------------------------------------------
The hostname executor's bind port(s) to and share with other executors/driver
(AM), is passed in as cli parameter for executor in case of apache spark.
Particularly in deployments with multiple interfaces and hostnames, it does not
try to determine which hostname to use : simply depend on what the resource
manager (yarn in this case) is configured with and shared with the container to
use.
Apache spark works across resource managers (standalone, mesos, k8s, yarn, etc)
and expects this to be determined by the individual resource manager it is
running on.
> 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
>
>
> 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]
