Thanks for quick response. That is very helpful. So, if I understand correctly, the framework should keep the entire offer, even only partial of the offer is satisfied the requirement ? For example, the framework asks for totally 4GB memory as role of prod. And the master gives the offer: such as 2GB in host1, and 2GB in host2. For some reasons (probably data locality. etc), the framework thinks that 2GB in host1 is acceptable. But the framework has to keep the entire offer, and send another resource request to ask another 2GB memory. When the framework gets all the resource and launch the tasks, the un-used resource will be released ? So, although the framework asks for totally 4GB memory, it actually holds for 6GB until it launches the tasks ?
Is this true ? Thanks Ying On Mon, Jul 6, 2015 at 4:25 PM, Connor Doyle <[email protected]> wrote: > Hi Ying, > > When launching tasks, the scheduler includes the resources to consume. > The remainder is implicitly declined. > Also, the scheduler can accept and merge multiple offers from the same > slave. > > -- > Connor > > > > On Jul 6, 2015, at 16:19, Ying Ji <[email protected]> wrote: > > > > Hey, mesos experts: > > > > I have a question about mesos resource allocation. If the framework > sends the resource request, the master will give the current best offer to > the framework (probably not the one which can satisfy the framework > completely). In this case, the framework can either accept the offer or > decline the offer. My question is: can the framework accept the partial > offer, and decline the other part ? > > > > > > Thanks > > > > Ying > >
