[
https://issues.apache.org/jira/browse/MESOS-9028?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Meng Zhu reassigned MESOS-9028:
-------------------------------
Assignee: Meng Zhu
> De-couple suppression API from clearing filters.
> ------------------------------------------------
>
> Key: MESOS-9028
> URL: https://issues.apache.org/jira/browse/MESOS-9028
> Project: Mesos
> Issue Type: Improvement
> Components: allocation, master, scheduler api
> Reporter: Benjamin Mahler
> Assignee: Meng Zhu
> Priority: Major
>
> Currently, we have the following semantics:
> SUPPRESS: stop sending additional offers to the scheduler
> REVIVE: resume sending additional offers to the scheduler AND clear all
> filters
> SUPPRESS is idempotent and can be retried without issue, however, since
> revive clears all filters, it is not idempotent and it is risky to call it
> periodically.
> Suppression state and filter management should be done with separate APIs,
> e.g.:
> SUPPRESS: stop sending additional offers to the scheduler
> UNSUPPRESS: resume sending additional offers to the scheduler
> CLEAR_FILTERS: clear filters
> REVIVE: (for backwards compatibility) UNSUPPRESS + CLEAR_FILTERS
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
