[
https://issues.apache.org/jira/browse/YARN-6161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16144292#comment-16144292
]
Eric Yang commented on YARN-6161:
---------------------------------
The current design supports host network, bridge network and fixed-cidr. The
possible combinations of port allocations are:
| Network Type | Port allocation method | YARN resource tracking |
| host | Random port | No action, OS handles port allocation |
| host | Fixed port | YARN tracks ports assignment |
| bridge | Random port | No action, OS handles port allocation |
| bridge | Fixed port | YARN map and track ports assignment |
| cidr | Random port | No action, OS handles port allocation |
| cidr | Fixed port | YARN tracks ports assignment |
Where bridge means container has private network address but port is exposed to
outside world on host network.
Where cidr means container is issued with IP from the same subnet as the host
network.
Bridge with random port is likely an unsupported configuration due to late
binding of port information by application and docker does not become aware of
the port existence. This feature requires tracking of port usage by
containers, and mapping port redirection for bridged network.
> YARN support for port allocation
> --------------------------------
>
> Key: YARN-6161
> URL: https://issues.apache.org/jira/browse/YARN-6161
> Project: Hadoop YARN
> Issue Type: Sub-task
> Reporter: Billie Rinaldi
> Fix For: yarn-native-services
>
>
> Since there is no agent code in YARN native services, we need another
> mechanism for allocating ports to containers. This is not necessary when
> running Docker containers, but it will become important when an agent-less
> docker-less provider is introduced.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
