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
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
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
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://i
