To clarify David's answer, you should only get <16, 8> offer until the filter on <0, 8> is active. Once the filter expires (or you call reviveOffers), Mesos will consolidate those resources and send a <16, 16> offer. You don't need to restart the master for the aggregation.
On Mon, Apr 6, 2015 at 10:46 AM, Itamar Ostricher <[email protected]> wrote: > Thanks David! > > I'd like to make sure I understand you correctly. > I will get both <16,8> & <0,8> offers, or just the <16,8> offer? (because > I previously rejected the <0,8> offer, and did not call reviveOffers) > > On Mon, Apr 6, 2015 at 3:06 PM, David Greenberg <[email protected]> > wrote: > >> You'll actually see that as 2 offers: <16,8> and <0,8>. Your framework >> may need to consolidate those offers if it requires more than 8gb of memory >> for the next task; you can do that by calling launchTasks with both offers. >> Besides combining offers in the framework, if you fail over the master, the >> offers would also be consolidated. >> On Mon, Apr 6, 2015 at 7:29 AM Itamar Ostricher <[email protected]> >> wrote: >> >>> Say my scheduler received a resource offers from slave S with <16cpu, >>> 16GiB mem>, and called launchTasks on this offer with utilization of >>> <16cpu, 8GiB mem>. >>> From what I see (with mesos 0.21), the left over <0cpu, 8GiB mem> is >>> considered rejected, and will be re-offered after the rejection filter, or >>> after I call reviveOffers. >>> >>> What I'm not sure about, is what happens when the task that was launched >>> completes, the rejection filter is still applicable, and I don't call >>> reviveOffers. >>> Once the <16cpu, 8GiB mem> is available, will I get these resources as >>> an offer, or will the master combine it with the other 8GiB mem and offer >>> me <16cpu, 16GiB> again? >>> >>> Thanks, >>> - Itamar. >>> >> >
