RE: Can Framework accept partial offers
I think framework will no hold 6G, because allocator will keep notify the framework for the offer; if framework did not launchTask, the un-used resource will return back to allocator and re-balance(DRF) between framework in next schedule cycle. Regards,Klaus Ma (马达), PMP® | http://www.cguru.net CallSend SMSCall from mobileAdd to SkypeYou'll need Skype CreditFree via SkypeCallSend SMSCall from mobileAdd to SkypeYou'll need Skype CreditFree via Skype Date: Sat, 25 Jul 2015 08:44:25 +0800 Subject: Re: Can Framework accept partial offers From: zhq527...@gmail.com To: user@mesos.apache.org I think it is Mesos allocator to offer resources and it is up to framework scheduler to accept resources in the offer or decline. 2015-07-07 8:18 GMT+08:00 Vinod Kone : Mesos doesn't currently support the notion of requesting resources. Resources are offered by Mesos based on a fair sharing algorithm (DRF) and it is up to the allocator to accept (partial) resources or decline. On Mon, Jul 6, 2015 at 5:00 PM, Ying Ji wrote: 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 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 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
Re: Can Framework accept partial offers
I think it is Mesos allocator to offer resources and it is up to framework scheduler to accept resources in the offer or decline. 2015-07-07 8:18 GMT+08:00 Vinod Kone : > Mesos doesn't currently support the notion of requesting resources. > Resources are offered by Mesos based on a fair sharing algorithm (DRF) and > it is up to the allocator to accept (partial) resources or decline. > > On Mon, Jul 6, 2015 at 5:00 PM, Ying Ji wrote: > >> 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 >> 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 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 >>> >>> >> >
Re: Build 0.23 gcc Version
Hi John, I would first suggest trying *CC="gcc" CXX="g++" ../configure*, and if that works, try to find out what *which* *cc* and *which* *c++* return and find out what they symlink to. I believe autotools uses *cc* and *c++* rather than *gcc* and *g++* by default, so I think there's probably something funky going on there. MPark. On Fri, Jul 24, 2015 at 2:31 PM Benjamin Hindman wrote: > Hey John, > > It appears that we're finding gcc 4.6.3 on your machine. Is it possible > that your autotools are hard coded to look for a gcc that is not the gcc > that you've installed and is on your path? > > At least for me I use devtoolset-2 and Software Collections (scl) and I > can get my machine into funky set ups where I've got a gcc 4.8 installed > but using autotools it picks the wrong compiler. > > Ben. > > On Fri, Jul 24, 2015 at 2:02 PM John Omernik wrote: > >> I am trying to build 0.23, I got the error below. I already installed >> gcc-4.8 and set my alternatives to work with 4.8 as you can see gcc >> --version returns the right version, where is the configure script pulling >> that data? Are there flags I could use to help it through the process? :) >> >> John >> >> >> >> configure: error: GCC 4.8 or higher required (found 4.6.3) >> >> darkness@hadoopmapr1:/opt/mapr/mesos/mesos-0.23.0/build$ gcc --version >> >> gcc (Ubuntu 4.8.1-2ubuntu1~12.04) 4.8.1 >> >> Copyright (C) 2013 Free Software Foundation, Inc. >> >> This is free software; see the source for copying conditions. There is NO >> >> warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR >> PURPOSE. >> >
Re: Build 0.23 gcc Version
Hey John, It appears that we're finding gcc 4.6.3 on your machine. Is it possible that your autotools are hard coded to look for a gcc that is not the gcc that you've installed and is on your path? At least for me I use devtoolset-2 and Software Collections (scl) and I can get my machine into funky set ups where I've got a gcc 4.8 installed but using autotools it picks the wrong compiler. Ben. On Fri, Jul 24, 2015 at 2:02 PM John Omernik wrote: > I am trying to build 0.23, I got the error below. I already installed > gcc-4.8 and set my alternatives to work with 4.8 as you can see gcc > --version returns the right version, where is the configure script pulling > that data? Are there flags I could use to help it through the process? :) > > John > > > > configure: error: GCC 4.8 or higher required (found 4.6.3) > > darkness@hadoopmapr1:/opt/mapr/mesos/mesos-0.23.0/build$ gcc --version > > gcc (Ubuntu 4.8.1-2ubuntu1~12.04) 4.8.1 > > Copyright (C) 2013 Free Software Foundation, Inc. > > This is free software; see the source for copying conditions. There is NO > > warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. >
Build 0.23 gcc Version
I am trying to build 0.23, I got the error below. I already installed gcc-4.8 and set my alternatives to work with 4.8 as you can see gcc --version returns the right version, where is the configure script pulling that data? Are there flags I could use to help it through the process? :) John configure: error: GCC 4.8 or higher required (found 4.6.3) darkness@hadoopmapr1:/opt/mapr/mesos/mesos-0.23.0/build$ gcc --version gcc (Ubuntu 4.8.1-2ubuntu1~12.04) 4.8.1 Copyright (C) 2013 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
