Currently (0.28+), the reserved resources are also account into quota. For your case, the framework will get the 50 reserved CPU and 50 CPU from "*"; the other 100 CPU will NOT offer to this framework even no other frameworks.
---- Da (Klaus), Ma (马达) | PMP® | Advisory Software Engineer Platform OpenSource Technology, STG, IBM GCG +86-10-8245 4084 | [email protected] | http://k82.me On Tue, May 10, 2016 at 1:42 AM, haosdent <[email protected]> wrote: > >Will it take the 50 CPUs from the reservations and just block another 50 > CPUs from other slaves within the cluster? > Is the framework written by yourself? This depends on how your framework > implement resourceOffers. Suppose you assign your framework with `bar` and > reserved by this role as well. You still could accept the offer which role > is "*" in `Scheduler::resourceOffers`. > > On Mon, May 9, 2016 at 11:58 PM, Sebastian Kuepers < > [email protected]> wrote: > >> Hi, >> >> >> I have a framework, wich I want to guarantee ressources on my cluster - >> independently from the slaves. >> >> Let's say 100 CPU on a 200 CPU cluster. >> >> >> I could very well use quotas for that. I create a role for this framework >> and create the quota for this role with the 100 CPUs. >> >> >> But in my cluster I have a couple of slaves, which are great for the >> framework to run on, because they have a lot of memory for example. >> >> >> But they can only provide 50 of the 100 CPU I want to get for sure for >> this framework. >> >> So I would do start these slaves with reservations for this role. >> >> >> Does the quota mechanism, now take this into account, when trying to >> block and allocate resources for this framework? >> >> >> Will it take the 50 CPUs from the reservations and just block another 50 >> CPUs from other slaves within the cluster? >> >> >> Thanks for you help, >> >> Sebastian >> >> >> >> >> >> >> ------------------------------------------------------------------------ >> Disclaimer The information in this email and any attachments may contain >> proprietary and confidential information that is intended for the >> addressee(s) only. If you are not the intended recipient, you are hereby >> notified that any disclosure, copying, distribution, retention or use of >> the contents of this information is prohibited. When addressed to our >> clients or vendors, any information contained in this e-mail or any >> attachments is subject to the terms and conditions in any governing >> contract. If you have received this e-mail in error, please immediately >> contact the sender and delete the e-mail. >> > > > > -- > Best Regards, > Haosdent Huang >
