You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@mesos.apache.org by Vinod Kone <vi...@gmail.com> on 2015/07/18 02:01:59 UTC
Are any allocator modules relying on requestResources() call?
requestResources() call was added to the scheduler driver a long time ago,
but was never implemented by the built-in hierarchical allocator. One of
the reasons for not implementing it was that it wasn't clear how it should
be used in the face of DRF.
I was thinking to remove the code dealing with requestResources from
master/allocator and drop the message in the scheduler driver (can't delete
for backwards compatibility). The idea is to add it to the new HTTP API
if/when a case arises.
Does anyone have issues with it? I'm mainly concerned with any allocator
modules out there which have implemented and/or rely on this call.
Re: Are any allocator modules relying on requestResources() call?
Posted by Vinod Kone <vi...@gmail.com>.
I see. Ok. We will keep the call and add support in the new API as well.
@vinodkone
> On Jul 17, 2015, at 10:47 PM, Gidon Gershinsky <GI...@il.ibm.com> wrote:
>
> Hi Vinod,
>
> Yes, we use this API in the allocator module we develop, it pretty
> fundamental for support of a wide range of policies in our mechanism!!
>
>
>
> Regards,
> Gidon
>
>
>
>
>
>
>
> From: Vinod Kone <vi...@gmail.com>
> To: dev <de...@mesos.apache.org>
> Date: 18/07/2015 03:03 AM
> Subject: Are any allocator modules relying on requestResources()
> call?
>
>
>
> requestResources() call was added to the scheduler driver a long time ago,
> but was never implemented by the built-in hierarchical allocator. One of
> the reasons for not implementing it was that it wasn't clear how it should
> be used in the face of DRF.
>
> I was thinking to remove the code dealing with requestResources from
> master/allocator and drop the message in the scheduler driver (can't
> delete
> for backwards compatibility). The idea is to add it to the new HTTP API
> if/when a case arises.
>
> Does anyone have issues with it? I'm mainly concerned with any allocator
> modules out there which have implemented and/or rely on this call.
>
Re: Are any allocator modules relying on requestResources() call?
Posted by Gidon Gershinsky <GI...@il.ibm.com>.
Hi Vinod,
Yes, we use this API in the allocator module we develop, it pretty
fundamental for support of a wide range of policies in our mechanism!!
Regards,
Gidon
From: Vinod Kone <vi...@gmail.com>
To: dev <de...@mesos.apache.org>
Date: 18/07/2015 03:03 AM
Subject: Are any allocator modules relying on requestResources()
call?
requestResources() call was added to the scheduler driver a long time ago,
but was never implemented by the built-in hierarchical allocator. One of
the reasons for not implementing it was that it wasn't clear how it should
be used in the face of DRF.
I was thinking to remove the code dealing with requestResources from
master/allocator and drop the message in the scheduler driver (can't
delete
for backwards compatibility). The idea is to add it to the new HTTP API
if/when a case arises.
Does anyone have issues with it? I'm mainly concerned with any allocator
modules out there which have implemented and/or rely on this call.