You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Meng Zhu (JIRA)" <ji...@apache.org> on 2019/06/21 17:19:00 UTC

[jira] [Assigned] (MESOS-9601) Guard against downgrade hazards after new quota configurations are used.

     [ https://issues.apache.org/jira/browse/MESOS-9601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Meng Zhu reassigned MESOS-9601:
-------------------------------

    Assignee: Meng Zhu

> Guard against downgrade hazards after new quota configurations are used.
> ------------------------------------------------------------------------
>
>                 Key: MESOS-9601
>                 URL: https://issues.apache.org/jira/browse/MESOS-9601
>             Project: Mesos
>          Issue Type: Task
>            Reporter: Meng Zhu
>            Assignee: Meng Zhu
>            Priority: Major
>              Labels: resource-management
>
> Current (old) masters only support quota guarantee which also servers as limits implicitly. Once new masters start to support both guarantees and limits, there is no safe downgrade path without altering the cluster behavior (if the new quota semantics are used). Thus, we need to ensure that alerts are given if such downgrades are attempted.
> To this end, if the new `UPDATE_QUOTA` call is used, a new minimum capability `QUOTA_LIMITS` will be persisted to the registry along with the new `QuotaConfig` message. Thanks to the minimum capability check, old masters (that do not possess the `QUOTA_LIMITS` capability) will refuse the start in this case and we will print out suggestions to the operator.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)