The interaction between a scheduler and Mesos as I understand is:
while(true): //resourceOffers method Mesos sends a list of Offers to the scheduler. Each Offer contains resource info of a Mesos worker. Scheduler determine what to do with the list of offers continue My question is, when Mesos sends a new list of offers, are previous offers still valid? Is the scheduler being a good citizen by caching offers and launching it later, after other offer lists are received? Assuming no offerRecinced is called. The reason I ask is that I noticed in some cases Mesos may break down available resources in different offerings. Say there are 3 workers in the cluster (mesos1, mesos2, mesos3). After some time the schedule may see: *[offer1: mesos1, offer2: mesos2]* *(2 seconds later)* *[offer1: mesos3]* *(2 seconds later)* *(repeat)* As a schedule, I believe I can use all 3 offers to launch a big task. Is this true? -- Lin Zhao https://wiki.groupondev.com/Message_Bus 3101 Park Blvd, Palo Alto, CA 94306
