Hi Ben, I see. i was mistakenly assuming that once a got a new set of offers (via Scheduler.resourceOffers) that the previous set of Offers would be automatically rescinded or essentially no longer valid for my framework to use.
Currently my Frameworks processes one set of offers at a time (without blocking the Scheduler), so this does not sound like a big concern for me at the moment unless I get into aggregating offers across multiple Scheduler.resourceOffer calls. Thanks, Sam Taha http://www.grandlogic.com On Wed, Oct 16, 2013 at 12:52 PM, Benjamin Hindman < benjamin.hind...@gmail.com> wrote: > Hi Sam, > > > This enhancement, is implying it is currently possible for Mesos to > > deliver, to a single Framework, multiple Offers (with mutually exclusive > > resources) from the same slave? > > A single collection of offers delivered to a framework via the > Scheduler.resourceOffers callback will not include more than one offer per > slave. However, across multiple calls to the framework callback you may > have two offers for the same slave. If you decline both offers they can be > aggregated and re-delivered from Mesos. This enhancement let's you > aggregate them on the scheduler side instead. > > Does that help? > > Ben. >