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

Resource provider manager should persist resource provider information

    XMLWordPrintableJSON

    Details

    • Type: Improvement
    • Status: Resolved
    • Priority: Major
    • Resolution: Done
    • Affects Version/s: 1.5.0
    • Fix Version/s: 1.6.0
    • Component/s: storage
    • Labels:

      Description

      Currently, the resource provider manager used to abstract away resource provider subscription and state does not persist resource provider information. It has no notion of e.g., disconnected or forcibly removed resource providers. This makes it hard to implement a number of features, e.g.,

      • removal of a resource provider and make it possible to garbage collect its cached state (e.g., in the resource provider manager, agent, or master), or
      • controlling resource provider resubscription, e.g., by observing and enforcing resubscription timeouts.

      We should extend the resource provider manager to persist the state of each resource provider (e.g., CONNECTED, DISCONNECTED, its resources and other attributes). This information should also be exposed in resource provider reconciliation, and be reflected in master or agent endpoints.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                bbannier Benjamin Bannier
                Reporter:
                bbannier Benjamin Bannier
                Shepherd:
                Chun-Hung Hsiao
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: