[jira] [Commented] (MESOS-3826) Add an optional unique identifier for resource reservations

["Neil Conway (JIRA)" <ji...@apache.org>]

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

Neil Conway commented on MESOS-3826:
------------------------------------

There are some subtle issues here. Right now, reservations do not have identity. For example, suppose a slave has 8 CPUs and 8192 MB of RAM, and a framework makes two dynamic reservations for 2 CPUs and 2048 MB of RAM for role 'foo'. The result is that 4 CPUs and 4096MB of RAM on that slave are reserved for 'foo': there are *not* two distinct reservations that might themselves be assigned an ID.

Offhand, my initial impression is that this ticket would not be a reasonable thing to implement (unless we redefine how reservations work).

> Add an optional unique identifier for resource reservations
> -----------------------------------------------------------
>
>                 Key: MESOS-3826
>                 URL: https://issues.apache.org/jira/browse/MESOS-3826
>             Project: Mesos
>          Issue Type: Improvement
>          Components: general
>            Reporter: Sargun Dhillon
>            Assignee: Guangya Liu
>            Priority: Minor
>              Labels: mesosphere
>
> Thanks to the resource reservation primitives, frameworks can reserve resources. These reservations are per role, which means multiple frameworks can share reservations. This can get very hairy, as multiple reservations can occur on each agent. 
> It would be nice to be able to optionally, uniquely identify reservations by ID, much like persistent volumes are today. This could be done by adding a new protobuf field, such as Resource.ReservationInfo.id, that if set upon reservation time, would come back when the reservation is advertised.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)