mesos-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Benjamin Bannier (JIRA)" <>
Subject [jira] [Assigned] (MESOS-8402) Resource provider manager should persist resource provider information
Date Wed, 21 Mar 2018 12:23:00 GMT


Benjamin Bannier reassigned MESOS-8402:

    Assignee: Benjamin Bannier

> Resource provider manager should persist resource provider information
> ----------------------------------------------------------------------
>                 Key: MESOS-8402
>                 URL:
>             Project: Mesos
>          Issue Type: Improvement
>          Components: storage
>    Affects Versions: 1.5.0
>            Reporter: Benjamin Bannier
>            Assignee: Benjamin Bannier
>            Priority: Major
>              Labels: mesosphere
> 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,
> * 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
> 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.

This message was sent by Atlassian JIRA

View raw message