Uploaded image for project: 'Mesos'
  1. Mesos
  2. MESOS-9028

De-couple suppression API from clearing filters.

    XMLWordPrintableJSON

    Details

    • Type: Improvement
    • Status: In Progress
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Labels:
      None
    • Sprint:
      Resource Mgmt R8 Sprint 34
    • Story Points:
      5

      Description

      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

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                mzhu Meng Zhu
                Reporter:
                bmahler Benjamin Mahler
                Shepherd:
                Benjamin Mahler
              • Votes:
                0 Vote for this issue
                Watchers:
                6 Start watching this issue

                Dates

                • Created:
                  Updated: