Re: Dynamic Reservations

Yup, working on addressing all of the comments! Thanks for leaving them, everyone. Also, as @serb correctly pointed out (and Josh found out) I submitted an updated patch [1] with updated design document [2] [1] https://reviews.apache.org/r/57487/ [2] https://docs.google.com/document/d/1L2EKEcKKBP

Re: Dynamic Reservations

Dmitriy, There's a fair number of comments both here and on the doc. Will you have time to respond to these so we can find a path forward? Cheers, Joshua On Wed, Mar 8, 2017 at 8:44 PM, David McLaughlin wrote: > Ticket for replace task primitive already exists: > https://issues.apache.org/jir

Re: Dynamic Reservations

Ticket for replace task primitive already exists: https://issues.apache.org/jira/browse/MESOS-1280 On Wed, Mar 8, 2017 at 6:34 PM, David McLaughlin wrote: > Spoke with Zameer offline and he asked me to post additional thoughts > here. > > My motivation for solving this without dynamic reservatio

Re: Dynamic Reservations

Spoke with Zameer offline and he asked me to post additional thoughts here. My motivation for solving this without dynamic reservations is just the sheer number of questions I have after reading the RFC and current design doc. And most of them are not about the current proposal and goals or the MV

Re: Dynamic Reservations

You don't have to store anything with my proposal. Preemption doesn't store anything either. The whole thing is it's just best-effort, and if the Scheduler restarts the worst that would happen is part of the current batch would have to go through the current Scheduling loop that users tolerate and

Re: Dynamic Reservations

David, I have two concerns with that idea. First, it would require persisting the relationship of to for every task. I'm not sure if adding more storage and storage operations is the ideal way of solving this problem. Second, in a multi framework environment, a framework needs to use dynamic res

Re: Dynamic Reservations

So I read the docs again and I have one major question - do we even need dynamic reservations for the current proposal? The current goal of the proposed work is to keep an offer on a host and prevent some other pending task from taking it before the next scheduling round. This exact problem is sol

Re: Dynamic Reservations

I read over the docs, it looks like a good start. Personally I don't see much of a benefit for dynamically reserved cpu/mem, but I'm excited about the possibility of building off this for dynamically reserved persistent volumes. I would like to see more detail on how a reservation "times out", an

Re: Dynamic Reservations Update

Update: If there are no major issues that get raised by tomorrow afternoon, then I will start cutting JIRA tasks for this feature. Thanks everyone! On Fri, Nov 4, 2016 at 10:23 AM Dmitriy Shirchenko wrote: > Hi everyone! > > I would like to share the DR design >