Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Date: Fri, 27 May 2016 05:04:13 +0000 (UTC)
From: "Jun Gong (JIRA)" <jira@apache.org>
To: yarn-issues@hadoop.apache.org
Message-ID: <JIRA.12973278.1464317431000.312489.1464325453098@Atlassian.JIRA>
In-Reply-To: <JIRA.12973278.1464317431000@Atlassian.JIRA>
References: <JIRA.12973278.1464317431000@Atlassian.JIRA> <JIRA.12973278.1464317431853@arcas>
Subject: [jira] [Commented] (YARN-5168) Add port mapping handling when
 docker container use bridge network
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Fri, 27 May 2016 05:04:15 -0000


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

Jun Gong commented on YARN-5168:
--------------------------------

{quote}
1. For item3, do you mean adding DNS like service registry in YARN or just provide API for querying container port on the host (container.getNodeId().getPort())?
{quote}
We could get container's mapped port on the host by {{docker inspect}} first, then register it to ZK/ETCD/.. like YARN-913. Like what you said, we could add DNS service for docker apps, however IIUC DNS are mainly used for resolving IP, for bridge network, we could not get container's mapped port on host by DNS. There are other network types(ip mode or overlay network) which could resolve the problem.

{quote}
2.We know that YARN provides network IO isolation ( traffic only ) in YARN-2140. But what I'm thinking is that the SLA stuffs may be delegated to Docker because it's possible that Docker network plugin will provide such ability in future.
{quote}
Actually we could delegate it to docker or set cgroups directly. If we do it in docker, we will depend on docker's new version.

{quote}
And the network ports seems can be one kind of resource too (in bridge mode)?
{quote}
For host mode, port mapping might conflict for each container, however I think the problem does not exist for bridge mode.

> Add port mapping handling when docker container use bridge network
> ------------------------------------------------------------------
>
>                 Key: YARN-5168
>                 URL: https://issues.apache.org/jira/browse/YARN-5168
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>            Reporter: Jun Gong
>
> YARN-4007 addresses different network setups when launching the docker container. We need support port mapping when docker container uses bridge network.
> The following problems are what we faced:
> 1. Add "-P" to map docker container's exposed ports to automatically.
> 2. Add "-p" to let user specify specific ports to map.
> 3. Add service registry support for bridge network case, then app could find each other. It could be done out of YARN, however it might be more convenient to support it natively in YARN.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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