[
https://issues.apache.org/jira/browse/MESOS-3826?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15021979#comment-15021979
]
Neil Conway commented on MESOS-3826:
------------------------------------
You don't _need_ an ID: the status quo is that your framework needs to compare
the resources it is offered with the resources it has tried to reserve, and
then it should either make additional reservations or unreserve duplicate
reservations as necessary.
Adding reservation request IDs (likely along with some notion of
"reconciliation" for those IDs) might make this simpler, though.
> 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, reservations
>
> 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)
