hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Shane Kumpf (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-7987) Docker container name(--name) needs to be DNS friendly for DNS resolution to work in user defined networks.
Date Thu, 01 Mar 2018 14:00:02 GMT

    [ https://issues.apache.org/jira/browse/YARN-7987?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16382029#comment-16382029
] 

Shane Kumpf commented on YARN-7987:
-----------------------------------

[~suma.shivaprasad] Thanks for reporting this. It's really a shame that Docker doesn't honor
the hostname here. 

IIRC, with an overlay network, the FQDN is {{<container_name>.<network name>}},
not the domain defined in YARN DNS. Is that not the case when {{\-\-name}} is fully qualified?


Have you looked into the {{\-\-network-alias}} option? I think this will associate an additional
"alias" hostname with the container's default hostname (like a CNAME). If you set that to
the same value as {{\-\-hostname}}, that might deal with the resolution issues. Can we first
explore if that might work?



> Docker container name(--name) needs to be DNS friendly for DNS resolution to work in
user defined networks. 
> ------------------------------------------------------------------------------------------------------------
>
>                 Key: YARN-7987
>                 URL: https://issues.apache.org/jira/browse/YARN-7987
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>            Reporter: Suma Shivaprasad
>            Assignee: Suma Shivaprasad
>            Priority: Major
>
> User defined networks like overlays support DNS resolution through Docker Embedded DNS
which needs the container name (–name parameter value in docker run) to be a FQDN for container
names to be resolved - Please refer documentation [https://docs.docker.com/v17.09/engine/userguide/networking/configure-dns/]
> However Yarn sets the container name to the container's id which is not DNS friendly(eg: container_e26_1519402686002_0035_01_000003)
and is not a FQDN. 
> The proposal is to set a FQDN(eg: ctr-e26-1519402686002-0035-01-000003.domain-name)
as the docker container's name for containers to be able to communicate to each other via
hostnames in user defined networks like overlays, bridges etc. The domain name will be picked
up from the YARN DNS registry configuration (hadoop.registry.dns.domain-name)
>  
>  
>  
>  
>  
>  
>  
>  



--
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


Mime
View raw message