[
https://issues.apache.org/jira/browse/MESOS-9820?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16864550#comment-16864550
]
Meng Zhu commented on MESOS-9820:
---------------------------------
{noformat}
commit 4703b23143ee806ed5e68d9ff6eabe9600ffc9c9
Author: Meng Zhu <m...@mesosphere.io>
Date: Wed Jun 5 16:44:00 2019 -0700
Added `updateQuota` method to the allocator.
This call updates a role's quota guarantees and limits.
All roles have a default quota defined as `DEFAULT_QUOTA`.
Currently, it is no guarantees and limits. Thus to "remove"
a quota, one should simply update the quota to be
`DEFAULT_QUOTA`.
Master `setQuota` and `removeQuota` calls into the allocator
are replaced with the `updateQuota`.
`setQuota` and `removeQuota` calls are now only used in the tests.
They will be removed once those tests are refactored.
Also fixed affected tests.
Review: https://reviews.apache.org/r/70803
{noformat}
> Add `updateQuota()` method to the allocator.
> --------------------------------------------
>
> Key: MESOS-9820
> URL: https://issues.apache.org/jira/browse/MESOS-9820
> Project: Mesos
> Issue Type: Improvement
> Components: allocation
> Reporter: Meng Zhu
> Assignee: Meng Zhu
> Priority: Major
> Labels: resource-management
>
> This is the method that underlies the `UPDATE_QUOTA` operator call. This will
> allow the allocator to set different values for guarantees and limits.
> The existing `setQuota` and `removeQuota` methods in the allocator will be
> deprecated. This will likely break many existing allocator tests. We should
> fix and refactor tests to verify the bursting up to limits feature.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
