Running Aurora next to other Frameworks

[Stephan Erb <st...@dev.static-void.de>]

Hi everybody,

as I have heard, Aurora is holding onto resource offers even without a
need for them at the moment. Why is this the case?

Does this mean we have to wait for optimistic resource offers [1] until
we can can run Aurora next to other frameworks on the same mesos
cluster? 

[1] https://issues.apache.org/jira/browse/MESOS-1607

Thanks for the info.

Best Regards,
Stephan

Re: Running Aurora next to other Frameworks

[Stephan Erb <st...@dev.static-void.de>]

Ok, thanks for the info! I will look into it.


On So, 2014-08-31 at 07:27 -0700, Bill Farner wrote:
> Long story short, holding offers is necessary to perform efficient
> scheduling and preemption.  You can tune the offer hold time with a command
> line argument (I'm not in front of my computer to check, but it's something
> like max_offer_hold_time).  I would not suggest pushing this much lower
> than 30 seconds or so.
> 
> On Sunday, August 31, 2014, Stephan Erb <st...@dev.static-void.de> wrote:
> 
> > Hi everybody,
> >
> > as I have heard, Aurora is holding onto resource offers even without a
> > need for them at the moment. Why is this the case?
> >
> > Does this mean we have to wait for optimistic resource offers [1] until
> > we can can run Aurora next to other frameworks on the same mesos
> > cluster?
> >
> > [1] https://issues.apache.org/jira/browse/MESOS-1607
> >
> > Thanks for the info.
> >
> > Best Regards,
> > Stephan
> >
> >
> >
> >
> >
> 

Re: Running Aurora next to other Frameworks

[Jay Buffington <me...@jaybuff.com>]

To reiterate Bill's point about preemption: if you add a second
framework then when you submit jobs that have production=True Aurora
will kill jobs that have production=False (the default) unnecessarily.
Since Aurora will not have a complete view of all of the available
resources, it will think the cluster is full and start killing
non-prod jobs to make room for prod jobs.

Like you said, once optimistic offers are implemented in Mesos and
Aurora has been modified to take advantage of that feature, this won't
be an issue.

Jay

On Sun, Aug 31, 2014 at 7:27 AM, Bill Farner <wf...@apache.org> wrote:
> Long story short, holding offers is necessary to perform efficient
> scheduling and preemption.  You can tune the offer hold time with a command
> line argument (I'm not in front of my computer to check, but it's something
> like max_offer_hold_time).  I would not suggest pushing this much lower
> than 30 seconds or so.
>
> On Sunday, August 31, 2014, Stephan Erb <st...@dev.static-void.de> wrote:
>
>> Hi everybody,
>>
>> as I have heard, Aurora is holding onto resource offers even without a
>> need for them at the moment. Why is this the case?
>>
>> Does this mean we have to wait for optimistic resource offers [1] until
>> we can can run Aurora next to other frameworks on the same mesos
>> cluster?
>>
>> [1] https://issues.apache.org/jira/browse/MESOS-1607
>>
>> Thanks for the info.
>>
>> Best Regards,
>> Stephan
>>
>>
>>
>>
>>
>
> --
> -=Bill

Re: Running Aurora next to other Frameworks

[Bill Farner <wf...@apache.org>]

Long story short, holding offers is necessary to perform efficient
scheduling and preemption.  You can tune the offer hold time with a command
line argument (I'm not in front of my computer to check, but it's something
like max_offer_hold_time).  I would not suggest pushing this much lower
than 30 seconds or so.

On Sunday, August 31, 2014, Stephan Erb <st...@dev.static-void.de> wrote:

> Hi everybody,
>
> as I have heard, Aurora is holding onto resource offers even without a
> need for them at the moment. Why is this the case?
>
> Does this mean we have to wait for optimistic resource offers [1] until
> we can can run Aurora next to other frameworks on the same mesos
> cluster?
>
> [1] https://issues.apache.org/jira/browse/MESOS-1607
>
> Thanks for the info.
>
> Best Regards,
> Stephan
>
>
>
>
>

-- 
-=Bill