[
https://issues.apache.org/jira/browse/MESOS-9619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16783058#comment-16783058
]
Meng Zhu commented on MESOS-9619:
---------------------------------
[~nimi] The crash is due to a misconfiguration, thus a Mesos validation bug.
The accept call
[here|https://gist.github.com/nemosupremo/3b23c4e1ca0ab241376aa5b975993270]
specified port 777 in both the executor and the task. This leads to duplication
allocations that caused the allocator to crash.
> 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)
