[
https://issues.apache.org/jira/browse/MESOS-9619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16783689#comment-16783689
]
Meng Zhu commented on MESOS-9619:
---------------------------------
Additional validation on the master side is needed. We should validate that for
range and set type resources such as ports, the same resources should not be
specified more than once in the tasks and executors. Because unlike scalars,
[1, 2] + [1, 2] is still [1, 2]. This will mess up the allocator accounting.
Specifically for the port resources here, we need to check that if we are only
using the host network namespace (which is the default setting), if so, the
executor and tasks should have non-overlap port resources.
> 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.
> Assignee: Meng Zhu
> Priority: Blocker
> Labels: allocator, 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)
