Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Date: Fri, 14 Jul 2017 16:00:01 +0000 (UTC)
From: "Billie Rinaldi (JIRA)" <jira@apache.org>
To: yarn-issues@hadoop.apache.org
Message-ID: <JIRA.13086294.1499787942000.249220.1500048001436@Atlassian.JIRA>
In-Reply-To: <JIRA.13086294.1499787942000@Atlassian.JIRA>
References: <JIRA.13086294.1499787942000@Atlassian.JIRA> <JIRA.13086294.1499787942181@jira-lw-us.apache.org>
Subject: [jira] [Commented] (YARN-6804) Allow custom hostname for docker
 containers in native services
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
archived-at: Fri, 14 Jul 2017 16:00:08 -0000


    [ https://issues.apache.org/jira/browse/YARN-6804?page=3Dcom.atlassian.=
jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D16087=
517#comment-16087517 ]=20

Billie Rinaldi commented on YARN-6804:
--------------------------------------

bq. I think the check for if =E2=80=9CLOG.isInfoEnabled=E2=80=9D is not req=
uired
Most of the LOG.info checks in DockerLinuxContainerRuntime have LOG.isInfoE=
nabled() before them (not sure why), so I was trying to match those. Do you=
 think we should remove them all?

bq. the network parameter is not used, and the added NETWORK_TYPE_BRIDGE se=
ems also not used
You're right, I had a version of the patch where I only set the hostname wh=
en the network type was bridge, but then I read that docker hostname can be=
 set even if network is host, so I removed it.

bq. probably we can create a common util method in RegistryPathUtils
Good point. Actually there's already a method for that, we can just make en=
codeYarnID perform the ctr replacement as well.

> Allow custom hostname for docker containers in native services
> --------------------------------------------------------------
>
>                 Key: YARN-6804
>                 URL: https://issues.apache.org/jira/browse/YARN-6804
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: yarn-native-services
>            Reporter: Billie Rinaldi
>            Assignee: Billie Rinaldi
>             Fix For: yarn-native-services
>
>         Attachments: YARN-6804-yarn-native-services.001.patch, YARN-6804-=
yarn-native-services.002.patch
>
>
> Instead of the default random docker container hostname, we could set a m=
ore user-friendly hostname for the container. The default could be a hostna=
me based on the container ID, with an option for the AM to provide a differ=
ent hostname. In the case of the native services AM, we could provide the h=
ostname that would be created by the registry DNS server. Regardless of whe=
ther or not registry DNS is enabled, this would be a more useful hostname f=
or the docker container.


--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org