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 <ita...@yowza3d.com> 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. >
