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

Add agent HTTP API operator call to mark local resource providers as gone

    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Resolved
    • Critical
    • Resolution: Fixed
    • 1.5.0
    • 1.8.0
    • agent, storage
    • Mesosphere Sprint 2018-25, Mesosphere Sprint 2018-26, Mesosphere Sprint 2018-27, Mesosphere Sprint 2018-28, Mesosphere Sprint 2018-29, Mesosphere RI-6 Sprint 2018-30, Mesosphere RI-6 Sprint 2018-31, Storage R7 Sprint 33, Storage R8 Sprint 34, Storage R8 Sprint 35, Storage R9 Sprint 36, Storage R9 Sprint 37, Storage R10 Sprint 38
    • 3

    Description

      It is currently not possible to mark local resource providers as gone (e.g., after agent reconfiguration). As resource providers registered at earlier times could still be cached in a number of places, e.g., the agent or the master, the only way to e.g., prevent this cache from growing too large is to fail over caching components (to e.g., prevent an agent cache to update a fresh master cache during reconciliation).

      Showing unavailable and known to be gone resource providers in various endpoints is likely also confusing to users.

      We should add an operator call to mark resource providers as gone. While the entity managing resource provider subscription state is the resource provider manager, it still seems to make sense to add this operator call to the agent API as currently only local resource providers are supported. The agent would then forward the call to the resource provider manager which would transition its state for the affected resource provider, e.g., setting its state to GONE and removing it from the list of known resource providers, and then send out an update to its subscribers.

      Attachments

        Issue Links

          Activity

            People

              bbannier Benjamin Bannier
              bbannier Benjamin Bannier
              Chun-Hung Hsiao Chun-Hung Hsiao
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: