[
https://issues.apache.org/jira/browse/YARN-5168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15345220#comment-15345220
]
Sidharta Seethana commented on YARN-5168:
-----------------------------------------
YARN today does not dynamically allocate/manage ports for containers, nor does
it provide a way to return arbitrary container attributes back from the
executor layer. For this to work end to end (for example to avoid port
collisions), YARN also needs to add support for scheduling based on ports.
This makes adding port support specifically for bridge mode quite a large task.
Also, bridge mode itself has certain limitations - since the IPs assigned are
(usually) not externally routable, certain kinds of applications will run into
issues ( e.g applications/tasks that need both forward/reverse lookups to
work). IMO, using a container SDN (that allows containers to see each other and
the outside world to see them) along with a discovery mechanism (e.g YARN-4757)
is a better path forward.
> 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: [email protected]
For additional commands, e-mail: [email protected]
