[
https://issues.apache.org/jira/browse/MESOS-2734?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vinod Kone updated MESOS-2734:
------------------------------
Description:
The simplest way to add support for oversubscribed resources to the allocator
is to simply add them to the already existing 'Slave.total' and
'Slave.available' variables. It is easy to distinguish the revocable resources
by doing a .revocable() filter.
was:
Allocator maintains 'revocable' resources which keeps track of the currently
available revocable resources.
Revocable resources are added to the DRF sorter allocations much like regular
resources during recoverResources() and allocate().
The only difference is that, unlike regular resources, 'revocable' resources
are *not* updated in allocate() or recover(). They only get updated in
updateRevocableResources() call.
The 2 main consequences of this design are
--> Revocable resources are accounted for in fair sharing which is great.
--> Allocation for revocable resources only happens whenever there is a new
estimate from the slave.
Story Points: 5 (was: 13)
> Update allocator to allocate revocable resources
> ------------------------------------------------
>
> Key: MESOS-2734
> URL: https://issues.apache.org/jira/browse/MESOS-2734
> Project: Mesos
> Issue Type: Task
> Reporter: Vinod Kone
> Assignee: Vinod Kone
> Labels: twitter
>
> The simplest way to add support for oversubscribed resources to the allocator
> is to simply add them to the already existing 'Slave.total' and
> 'Slave.available' variables. It is easy to distinguish the revocable
> resources by doing a .revocable() filter.
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
