mesos-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Adam B (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MESOS-1995) Provide a way for frameworks to clear their resource filters
Date Fri, 15 Jan 2016 09:54:39 GMT

    [ https://issues.apache.org/jira/browse/MESOS-1995?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15101555#comment-15101555
] 

Adam B commented on MESOS-1995:
-------------------------------

How does `reviveOffers()` not solve this? I thought that had been around for a long time.

> Provide a way for frameworks to clear their resource filters
> ------------------------------------------------------------
>
>                 Key: MESOS-1995
>                 URL: https://issues.apache.org/jira/browse/MESOS-1995
>             Project: Mesos
>          Issue Type: Improvement
>            Reporter: Vinod Kone
>
> Frameworks can provide filters on resources via launchTasks() or declineOffers() but
there is no way for them to clear previously set filters. This makes it hard for frameworks
to play nicely in a multi-framework cluster. While, frameworks can keep declining offers it
makes more sense to give frameworks more control.
> Concrete example: The Jenkins framework currently disconnects itself when its build queue
is empty so that it doesn't keep receiving offers. This allows other frameworks to get resources
more quickly. This is a bit of a hack. It would be great if Jenkins can do this more explicitly
via an API call.
> We already have a no-op resourcesRequested() API call. I propose we just clear the filters
when we receive this on the allocator.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message