[
https://issues.apache.org/jira/browse/MESOS-3826?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14993681#comment-14993681
]
Alexander Rukletsov commented on MESOS-3826:
--------------------------------------------
Having reservations per role instead of per framework was intentional AFAIK. I
would suggest you to have a look at [this
thread|https://mail-archives.apache.org/mod_mbox/mesos-dev/201508.mbox/%3cof678bc63d.7eb914a6-on48257eb1.00830d62-48257eb2.0001f...@cn.ibm.com%3E]
and [the design
doc|https://docs.google.com/a/mesosphere.io/document/d/1e3j69pfBgtc8xM00DhcuiMl6ImkEB5na0TzOMyzrg8A/edit#heading=h.gohshgapnm3h]
for reasoning.
I also think labels can mitigate this issue, though it will still require
frameworks to collaborate.
> 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)
