Yes, it is suggested to use dynamic reservation or persistent volume, please refer to https://issues.apache.org/jira/browse/MESOS-4616 for detail.
Thanks, Guangya On Thu, Jun 2, 2016 at 9:33 PM, haosdent <[email protected]> wrote: > >How do I prevent the allocator from reducing the length of offers or is > there any way I can obtain the list of all available offers before the > allocator sends them to the framework? > > As I know, mesos didn't provide these. But I think you may try ( > dynamic-reservation)[ > https://github.com/apache/mesos/blob/master/docs/reservation.md#dynamic-reservation] > when your framework decide to accept a single offer. Mesos would send the > offer meet your requirement if resource available. > > On Thu, Jun 2, 2016 at 2:18 PM, Nihal Harish <[email protected]> > wrote: > >> I am facing the following problem: >> >> I have a framework that under certain conditions, might accept a single >> offer after requesting for offers ( might even be choosing the same offer >> after every request). >> The allocator then begins to send a single offer to the framework (based >> on the previous selection). >> >> I am able to get a different list of offers by declining sent offers, but >> I can not determine whether the allocator has decided to send a smaller >> offer list to the framework, or there is a genuine shortage of available >> resources to provide offers. >> >> How do I prevent the allocator from reducing the length of offers or is >> there any way I can obtain the list of all available offers before the >> allocator sends them to the framework? >> >> Thanks. >> Regards, >> Nihal >> > > > > -- > Best Regards, > Haosdent Huang >
