Hi Daniel, this depends on your framework: Mesos assumes that a framework is "well behaved", i.e. only requests the resources that it really needs. A framework can control this using SchedulerDriver::requestResources() call. Therefore a framework might not take all available resources of an agent. A resource offer may be offered to other frameworks, the first one to launch a task via SchedulerDriver::launchTasks will get them. If a framework does not accept/decline an offer in time, it might already be taken. If no accept/decline arrives at the master after a certain amount of time, these resources are made available again.
On Fri, Dec 4, 2015 at 10:44 AM, Daniel <dan...@abde.me> wrote: > Hi, I'm confused with Mesos's resource offering mechanism: > > (a) An offer includes all available resources in a slave node. > > (b) A framework would occupy the resources associated with an offer, > regardless of whether the resources were actually used to launch tasks, > unless the offer was explicitly declined by calling declineOffer(offerId). > > (c) An offer must be declined in its entirety. > > Then it seems that if a framework does not decline an offer from a slave > node, other frameworks have no access to the resources on the same slave > node. Am I correct? Can tasks from mulliple frameworks simultaneously run > on the same slave node? > > Thanks a lot :-) > -- *Jan Schlicht* Distributed Systems Engineer, Mesosphere
