I will be happy to shepherd this. Have you looked at MESOS-3037 <https://issues.apache.org/jira/browse/MESOS-3037> that was filed recently for essentially the same thing? We can add filters to that call too.
Do you want this in the current API (scheduler driver) or can you wait until the HTTP API comes out (ETA mid August)? If you can't wait, wait for me to land MESOS-3037 and add the suppressOffers() driver call. Btw, we are calling this "suppress" instead of "quiesce". If you've a better name, feel free to suggest. Now that I think about it, maybe "FILTER" call and "filterOffers()" message are better? On Fri, Jul 17, 2015 at 10:30 AM, James Peach <jor...@gmail.com> wrote: > Hi all, > > In our Mesos deployment, we end up with a lot of small frameworks (> 200) > that hit their targets and have to refuse a lot of unwanted resources. This > causes significant performance degradation and unnecessary memory use in > the hierarchical allocator. > > I'm proposing a new QuiesceOffers message that a framework can use to > suppress offers of unwanted resources. See MESOS-3075. This has basically > the same semantics as refusing resources with a filter, except that is it > explicit that the framework doesn't need any more resources. > > In addition to comments on the API, I'd also like to solicit a shepherd to > get this change committed :) > > thanks, > James
