You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@mesos.apache.org by "Meng Zhu (JIRA)" <ji...@apache.org> on 2019/02/27 01:32:00 UTC

[jira] [Commented] (MESOS-9608) Refactor and Improve `class ResourceQuantity`.

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

Meng Zhu commented on MESOS-9608:
---------------------------------

`ResourceQuantity` part:

https://reviews.apache.org/r/70061
https://reviews.apache.org/r/70062
https://reviews.apache.org/r/70063

> Refactor and Improve `class ResourceQuantity`.
> ----------------------------------------------
>
>                 Key: MESOS-9608
>                 URL: https://issues.apache.org/jira/browse/MESOS-9608
>             Project: Mesos
>          Issue Type: Improvement
>            Reporter: Meng Zhu
>            Priority: Major
>              Labels: resource-management
>
> Currently, the `ResourceQuantity` only provides a minimal map interface with no built-in arithmetic and contains operations. This makes it unwieldy.
> The intention was to avoid the ambiguities between "absent-means-zero" (guarantee like semantic) and "absent-means-infinite" (limits like semantic). Instead of only providing a minimal interface and leave the rest to the caller, we should provide two classes for each semantic:
> - "ResourceQuantities" will have "absent-means-zero" semantic
> - "ResourceLimits" will  have "absent-means-infinite" semantic
> We can have both classes derived from the current class (rename to "ResourceMap") to save some common logic.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)