[
https://issues.apache.org/jira/browse/MESOS-9619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16784660#comment-16784660
]
Meng Zhu commented on MESOS-9619:
---------------------------------
Simply check there is no overlap between the range and set resources should be
enough. If, say, the user is using some customized network namespace, no port
resources should be specified in the non-host namespace (because they are not
managed by Mesos), but simply check that there is no overlap should guard Mesos
master from crashing.
However, one caveat is that the non-host port resources will be accounted as
allocated by Mesos (which in fact is not, because they are two distinct
namespaces).
> Mesos Master Crashes with Launch Group when using Port Resources
> ----------------------------------------------------------------
>
> Key: MESOS-9619
> URL: https://issues.apache.org/jira/browse/MESOS-9619
> Project: Mesos
> Issue Type: Bug
> Components: allocation
> Affects Versions: 1.4.3, 1.7.1
> Environment:
> Testing in both Mesos 1.4.3 and Mesos 1.7.1
> Reporter: Nimi Wariboko Jr.
> Priority: Critical
> Labels: foundations, master, mesosphere
> Attachments: mesos-master.log, mesos-master.snippet.log
>
>
> Original Issue:
> [https://lists.apache.org/thread.html/979c8799d128ad0c436b53f2788568212f97ccf324933524f1b4d189@%3Cuser.mesos.apache.org%3E]
> When the ports resources is removed, Mesos functions normally (I'm able to
> launch the task as many times as possible, while it always fails continually).
> Attached is a snippet of the mesos master log from OFFER to crash.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
