You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@mesos.apache.org by "Alexander Rukletsov (JIRA)" <ji...@apache.org> on 2017/03/29 07:07:41 UTC

[jira] [Commented] (MESOS-3875) Account dynamic reservations towards quota.

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

Alexander Rukletsov commented on MESOS-3875:
--------------------------------------------

I think the situation you describe is MESOS-3338. AFAIK, authz partially addresses the issue but not allowing greedy frameworks do as many reservations as they possibly can.

> Account dynamic reservations towards quota.
> -------------------------------------------
>
>                 Key: MESOS-3875
>                 URL: https://issues.apache.org/jira/browse/MESOS-3875
>             Project: Mesos
>          Issue Type: Task
>          Components: allocation, master
>            Reporter: Alexander Rukletsov
>            Priority: Critical
>              Labels: mesosphere
>
> Dynamic reservations—whether allocated or not—should be accounted towards role's quota. This requires update in at least two places:
> * The built-in allocator, which actually satisfies quota;
> * The sanity check in the master.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)