[
https://issues.apache.org/jira/browse/MESOS-9653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16798357#comment-16798357
]
Tim Harper commented on MESOS-9653:
-----------------------------------
This sounds like an easy optimization for both the Mesos allocator and
frameworks.
One thing I wonder about is how this will be exposed as to why frameworks
aren't getting any offers.
> Allow framework to set `min_alloctable_resources` upon revival.
> ---------------------------------------------------------------
>
> Key: MESOS-9653
> URL: https://issues.apache.org/jira/browse/MESOS-9653
> Project: Mesos
> Issue Type: Improvement
> Components: allocation
> Reporter: Meng Zhu
> Priority: Major
> Labels: mesosphere, resource-management
>
> In MESOS-9523, we added per-framework allocatable resources matcher/filter
> where frameworks can specify in their `FrameworkInfo` when subscribing.
> Frameworks can have some control over the shape of the resource offer via
> this per-framework filters.
> Other than set the filters when subscribing, a natural workflow is to set
> these filters upon revival. Frameworks can set these filters to the resource
> quantity shape of the tasks they want to launch upon revival. If a framework
> specifies this in a revive call, all existing filters (accumulated when
> declining offers) and the current `min_alloctable_resources` filters will be
> cleared and replaced with the new specified `min_alloctable_resources` filter.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
