You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Joseph Wu (JIRA)" <ji...@apache.org> on 2016/09/26 18:00:22 UTC
[jira] [Commented] (MESOS-6225) mesos-docker-executor port
collision with container(network:host)
[ https://issues.apache.org/jira/browse/MESOS-6225?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15523759#comment-15523759 ]
Joseph Wu commented on MESOS-6225:
----------------------------------
Consider using this: http://mesos.apache.org/documentation/latest/port-mapping-isolator/
Without the isolator, ports are allocated on an honor-system. If an executor/task binds to a port it did not request, we don't do anything about it.
> mesos-docker-executor port collision with container(network:host)
> -----------------------------------------------------------------
>
> Key: MESOS-6225
> URL: https://issues.apache.org/jira/browse/MESOS-6225
> Project: Mesos
> Issue Type: Bug
> Components: containerization
> Affects Versions: 1.0.1
> Environment: ubuntu 14.04 LTS
> mesos 1.0.1
> Reporter: Wei Wei
>
> we implement a scheduler to launch a batch of data process worker in docker container, we use network: host and assign random picked port for the process worker and encounter a port collision problem:
> the port we choose for the container was taken by the mesos-docker-container.
> mesos-agent resource config:
> {"name":"ports","type":"RANGES","ranges":{"range": [{"begin":10000,"end":32000}]}}]
> root@xs35:lsof -i:31981
> COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
> mesos-doc 2835 root 8u IPv4 433237650 0t0 TCP 10.34.38.30:31981 (LISTEN)
> the port was taken by mesos-docker-executor and the framework still offer port resource 31981
> is there a way to set mesos-docker-executors port range?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)