[
https://issues.apache.org/jira/browse/MESOS-3826?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14995888#comment-14995888
]
Sargun Dhillon commented on MESOS-3826:
---------------------------------------
The other problem here is idempotence. If I as framework A create a
reservation, and for whatever reason that resource gets offered to framework B,
which holds it, I am going to time out, thinking my reservation failed. I need
to have an ID, that's forced to be unique, in order to get some level of
idempotence, given the current asynchronous nature of reservations.
> 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)
