[ 
https://issues.apache.org/jira/browse/MESOS-9619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16826532#comment-16826532
 ] 

Greg Mann commented on MESOS-9619:
----------------------------------

1.7.x branch:
{code}
commit 206e44006540a4d9487da1cb60b64e58b2bf2a51
Author: Meng Zhu <[email protected]>
Date:   Tue Feb 26 15:06:07 2019 -0800

    Added method `fromScalarResources` in `ResourceQuantities`.

    This method takes all the scalar type `Resource` entries in
    the `Resources` and combine them to a `ResourceQuantities`.
    Only the resource name and its scalar value are used and the
    rest of the meta-data is ignored. Non-scalar resource entries
    are silently dropped. Since internal resources are always
    validated to have positive scalar values, this conversion will
    always succeed.

    Also added a dedicated test.

    (cherry-picked from commit da1f95714f29165ea603ad109efae4e822c7408a)
{code}
{code}
commit a0eb394d44ecc7608a4c40aca8ee6beee943e41e
Author: Meng Zhu <[email protected]>
Date:   Tue Mar 12 15:25:25 2019 -0700

    Added `>`, `<` and `>=` operators to `Value::Scalar`.

    (cherry-picked from commit 393f39dd8ea49d0d70e2ca562d8e0a2ab88d5238)
{code}
{code}
commit 6aec558976df2d6f29a4a99dc3715acae6ec8992
Author: Meng Zhu <[email protected]>
Date:   Tue Feb 26 15:45:08 2019 -0800

    Refactored and augmented `class ResourceQuantities`.

    This patch removed the map interface of
    `class ResourceQuantities`, added a few built-in
    arithmetic operations. Now, absent resource items imply
    there is no (zero) such resources.

    Also added a to-do to add `class ResourceLimits` which
    is similar but treats absent resource entries as having
    infinite amount of such resource.

    Also changed affected call sites and tests accordingly.

    (cherry-picked from commit aa7b75fecd336b951fa8577ac5db26d3d0e28c1b)
{code}
{code}
commit 000aa6ea5e022435c3b55f6c4ca425601dc8e01f
Author: Meng Zhu <[email protected]>
Date:   Wed Mar 27 17:09:13 2019 -0700

    Added `==` and `!=` operator in `ResourceQuantities`.

    (cherry-picked from commit 7c8a9a9218b5b3a9a2acbf8c10899355773377ef)
{code}
{code}
commit 975066ad8438968df6edc325e90d6c9e2610f60e
Author: Greg Mann <[email protected]>
Date:   Fri Apr 19 00:34:15 2019 -0700

    Enabled construction of `ResourceQuantities` from `Resources`.

    This patch adds a new static method which enables the
    construction of `ResourceQuantities` from `Resources`.
    Namely, this permits the inclusion of sets and ranges in the
    input resources used to construct `ResourceQuantities`.

    (cherry-picked from commit cbae57b7e790b8b46c79052975406d603e7d175a)
{code}
{code}
commit 55ae37ee5a04a17c6f8c996d1c31681124782894
Author: Greg Mann <[email protected]>
Date:   Sat Apr 20 11:48:39 2019 -0700

    Ensured that task groups do not specify overlapping ranges or sets.

    This patch adds validation to the master to ensure that task
    groups do not include resources with overlapping set- or
    range-valued resources, as this can crash the allocator.

    (cherry-picked from commit f8ffdb7bbf3ff58e1e7a411cdd66767519d9a7ad)
{code}

> 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: Greg Mann
>            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)

Reply via email to