Sounds good, will do.
Regards,
Gidon
From: Alex Rukletsov
To: user@mesos.apache.org
Date: 17/08/2015 05:30 PM
Subject:Re: Launching tasks with reserved resources
> if there were an api for splitting a resource object
I think it's a good idea, "reso
two separate offers
> indeed helps here, since each offer comes with a single role.
> In any case, I agree it makes sense for a developer to be aware of the
> reservation policies.
>
>
>
> Regards,
> Gidon
>
>
>
>
>
>
.apache.org
Date: 17/08/2015 01:02 PM
Subject: Re: Launching tasks with reserved resources
Hi Gidon,
just to make sure, you mean static reservations on mesos agents (via
--resources flag) and not dynamic reservations, right?
Let me first try to explain, why you get the TASK_ERR
Hi Gidon,
just to make sure, you mean static reservations on mesos agents (via
--resources flag) and not dynamic reservations, right?
Let me first try to explain, why you get the TASK_ERROR message. The
built-in allocator merges '*' and reserved resources, hinting master to
create a single offer.
I have a simple setup where a framework runs with a role, and some
resources are reserved in cluster for that role.
The resource offers arrive at the framework as a list of two resource
sets: one general (cpus(*)), etc) and one specific for the role
(cpus("role1"), etc).
So far so good. If two
5 matches
Mail list logo
