mesos-reviews mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael Park" <mcyp...@gmail.com>
Subject Re: Review Request 32982: Added reservation user guide.
Date Fri, 26 Jun 2015 17:02:34 GMT


> On May 8, 2015, 7:02 p.m., Timothy Chen wrote:
> > docs/reservation.md, line 243
> > <https://reviews.apache.org/r/32982/diff/1/?file=921006#file921006line243>
> >
> >     What happens if you try to unreserve a reservation that is being used right
now?

The reason why we go through the offer cycle is to eliminate the case where a framework could
attempt to unreserve resources that are being used. That is, we know that the resources are
not used because the framework was offered them.

There are ways when the offer becomes invalid however. For example if it is rescinded, in
the future it's possible that we're racing with another framework via optimistic offers. In
these cases, the behavior will stay consistent with `LaunchTasks`. Currently the master just
logs/drops invalid operations.


- Michael


-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/32982/#review83054
-----------------------------------------------------------


On June 26, 2015, 4:54 p.m., Michael Park wrote:
> 
> -----------------------------------------------------------
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/32982/
> -----------------------------------------------------------
> 
> (Updated June 26, 2015, 4:54 p.m.)
> 
> 
> Review request for mesos, Alexander Rukletsov, Jie Yu, and Timothy Chen.
> 
> 
> Bugs: MESOS-2205
>     https://issues.apache.org/jira/browse/MESOS-2205
> 
> 
> Repository: mesos
> 
> 
> Description
> -------
> 
> See summary.
> 
> NOTE: The framework API should be reviewed thoroughly at this point since those have
been implemented and landed.
>       The master API endpoints however are still in development and therefore the state
reflected in this patch is incomplete. (e.g. what HTTP code do we return on failures?)
>       I'll update the guide to accurately reflect the master endpoints as it gets more
solified.
>       The purpose of including it was/is to get initial feedback on how it generally
works.
> 
> 
> Diffs
> -----
> 
>   docs/reservation.md PRE-CREATION 
> 
> Diff: https://reviews.apache.org/r/32982/diff/
> 
> 
> Testing
> -------
> 
> Documentation.
> 
> 
> Thanks,
> 
> Michael Park
> 
>


Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message