You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-issues@hadoop.apache.org by "Suma Shivaprasad (JIRA)" <ji...@apache.org> on 2018/10/04 23:14:00 UTC
[jira] [Commented] (YARN-7935) Expose container's hostname to
applications running within the docker container
[ https://issues.apache.org/jira/browse/YARN-7935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16639019#comment-16639019 ]
Suma Shivaprasad commented on YARN-7935:
----------------------------------------
This is no longer needed since the container's hostname, IP and additional information could be obtained via YARN-8659 by Spark or other AMs which need this information.
> 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: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org