[
https://issues.apache.org/jira/browse/MESOS-8968?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16891417#comment-16891417
]
Meng Zhu commented on MESOS-8968:
---------------------------------
{noformat}
commit 7aa2a96fea8a44f673a95b425bae71c946c09f2c (HEAD -> update_quota_working,
apache/master)
Author: Meng Zhu <[email protected]>
Date: Thu Jul 18 11:32:49 2019 -0700
Added a test to ensure `UPDATE_QUOTA` is applied all-or-nothing.
Review: https://reviews.apache.org/r/71119
{noformat}
> Wire `UPDATE_QUOTA` call.
> -------------------------
>
> Key: MESOS-8968
> URL: https://issues.apache.org/jira/browse/MESOS-8968
> Project: Mesos
> Issue Type: Bug
> Reporter: Meng Zhu
> Assignee: Meng Zhu
> Priority: Major
> Labels: Quota, allocator, multitenancy
>
> Wire the existing master, auth, registar, and allocator pieces together to
> complete the `UPDATE_QUOTA` call.
> This would enable the master capability `QUOTA_V2`.
> This also fixes the "ignoring zero resource quota" bug in the old quota
> implementation, namely:
> Currently, Mesos discards resource object with zero scalar value when parsing
> resources. This means quota set to zero would be ignored and not enforced.
> For example, role with quota set to "cpu:10;mem:10;gpu:0" intends to get no
> GPU. Due to the above issue, the allocator can only see the quota as
> "cpu:10;mem:10", and no quota GPU means no guarantee and NO limit. Thus GPUs
> may still be allocated to this role.
> With the completion of `UPDATE_QUOTA` which takes a map of name, scalar
> values, zero value will no longer be dropped.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
