[
https://issues.apache.org/jira/browse/MESOS-3875?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Mahler updated MESOS-3875:
-----------------------------------
Priority: Critical (was: Major)
Not accounting them when not allocated seems to allow gaming of the quota
system.
The scenario is: I keep making reservations, I filter out any reservations that
come back, in an effort to amass as many reserved resources as possible. Can I
reserve the whole cluster this way given we don't count the reserved resources
towards the qutoa? Or is there something in place already that is preventing
this?
> 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)
