mesos-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Vinod Kone <>
Subject Re: Setting Rate of Resource Offers
Date Wed, 17 Jun 2015 17:18:21 GMT
Can you paste the master logs for when the task is finished and the next
offer is sent?

On Wed, Jun 17, 2015 at 9:11 AM, Christopher Ketchum <>

> Hi everyone,
> Thanks for the responses. To clarify, I’m only running one framework with
> a single slave for testing purposes, and it is the re-offers that I am
> trying to adjust. When I watch the program run I see tasks updating to
> TASK_FINISHED, but there is a noticeable delay where my framework has the
> next task queued but the master has not yet reoffered those resources, so
> the program pauses until it gets the next offer.
> I am mainly concerned that I haven’t configured something properly, and
> when I scale up the delays will compound. Of course, it is also possible
> that with multiple slaves able to offer resources these delays will
> disappear.
> Thanks again,
> Christopher
> On Jun 14, 2015, at 8:11 AM, Alex Gaudio <> wrote:
> Hi Christopher,
> To let a particular mesos framework receive more offers than other
> frameworks, we assign our frameworks weights.  The higher the weight, the
> more frequently the framework will receive an offer.  See the '--weights'
> and '--roles' options in the config:
>  Basically,
> a higher weight > 1 means more offers get sent to your framework.  The
> mesos source code for how weighting works is shown here:
> and
> .
> What you may want to do is create a "role" called "development_mode" and
> then assign the role a high weight (like 40).  You would then assign your
> framework to the "development_mode" role.  What we've actually done is
> created roles named the numbers 1,2,3,4,5,10,20,30,40, where each role maps
> to a weight of that number ... and we then we allow frameworks to choose
> which role they start up as.  At Mesoscon, I will be speaking about why we
> do this and how we are solving some general issues with the DRF algorithm,
> if you're interested!
> Alex
> On Sun, Jun 14, 2015 at 5:58 AM Alex Rukletsov <>
> wrote:
>> Christopher,
>> try adjusting master allocation_interval flag. It specifies often the
>> allocator performs batch allocations to frameworks. As Ondrej pointed out,
>> if you framework explicitly declines offers, it won't be re-offered the
>> same resources for some period of time.
>> On Sat, Jun 13, 2015 at 8:30 PM, Ondrej Smola <>
>> wrote:
>>> Hi Christopher,
>>> i dont know about any way way how to speed up first resource offer -
>>> in my experience new offers arrive almost immediately after framework
>>> registration. It depends on the infrastructure you are testing your
>>> framework on - are there any
>>> other frameworks running? As is discussed in an another thread offers
>>> should be send to multiple frameworks at once. There may be small
>>> delay based on initial registration and network delay. If you speak
>>> about "reoffers" - reoffering
>>> decline offers - there should param to set interval for reoffer. For
>>> example in Go you can decline offer this way (it is also important to
>>> decline every non used offer):
>>> driver.DeclineOffer(offer.Id, &mesos.Filters{RefuseSeconds:
>>> proto.Float64(5)})
>>> Look to mesos UI - it shoud give you information abou what offers are
>>> offered to which frameworks, mesos master logs also give you this
>>> information.
>>> 2015-06-13 18:23 GMT+02:00 Christopher Ketchum <>:
>>> > Hi,
>>> >
>>> > I was wondering if there was any way to adjust the rate of resource
>>> offers to the framework. I am writing a mesos framework, and when I am
>>> testing it I am noticing a slight pause were the framework seems to be
>>> waiting for another resource offer. I would like to know if there is any
>>> way to speed these offers up, just to make testing a little faster.
>>> >
>>> > Thanks,
>>> > Chris

View raw message