Details
-
Documentation
-
Status: Open
-
Major
-
Resolution: Unresolved
-
None
-
None
Description
With MESOS-6432 we changed the behavior of quota: now a quota is considered satisfied if a single resource kind in the quota vector was allocated to the quotaed value.This also slightly changed the notion of quota in the interplay of guarantee and limit.
For frameworks with use patterns similar to the set quota the original behavior is preserved; for frameworks with use patterns wildly different than the quota however the new behavior can lead to possibly surprising behavior (e.g., unexpectedly low number of offers after a component in the quota vector reaches its nominal value).
We should make sure the documentation prominently calls out the new behavior, and encourages operators and framework developers to monitor their frameworks' usage pattern in order to set reasonable quotas. We should also check that the documentation paints a correct picture of quota in the context of guarantee and limit.
Attachments
Issue Links
- is related to
-
MESOS-6432 Roles with quota assigned can "game" the system to receive excessive resources.
- Resolved