You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Klaus Ma (JIRA)" <ji...@apache.org> on 2016/07/09 10:49:12 UTC

[jira] [Updated] (MESOS-4967) Oversubscription for reservation

     [ https://issues.apache.org/jira/browse/MESOS-4967?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Klaus Ma updated MESOS-4967:
----------------------------
    Assignee:     (was: Klaus Ma)

> Oversubscription for reservation
> --------------------------------
>
>                 Key: MESOS-4967
>                 URL: https://issues.apache.org/jira/browse/MESOS-4967
>             Project: Mesos
>          Issue Type: Epic
>          Components: allocation, framework, master
>            Reporter: Klaus Ma
>              Labels: IBM, mesosphere
>
> Reserved resources allow frameworks and cluster operators to ensure sufficient resources are available when needed.  Reservations are usually made to guarantee there are enough resources under peak loads. Often times, reserved resources are not actually allocated; in other words, the frameworks do not use those resources and they sit reserved, but idle.
> This underutilization is either an opportunity cost or a direct cost, particularly to the cluster operator.  Reserved but unallocated resources held by a Lender Framework could be optimistically offered to other frameworks, which we refer to as Tenant Frameworks.  When the resources are requested back by the Lender Framework, some of the Tenant Framework’s tasks are evicted and the original resource offer guarantee is preserved.
> The first step is to identify when resources are reserved, but not allocated.  We then offer these reserved resources to other frameworks, but mark these offered resources as revocable resources.  This allows Tenant Frameworks to use these resources temporarily in a 'best-effort' fashion, knowing that they could be revoked or reclaimed at any time.



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