mesos-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Benjamin Bannier (JIRA)" <>
Subject [jira] [Assigned] (MESOS-8403) Add agent HTTP API operator call to mark local resource providers as gone
Date Mon, 30 Jul 2018 09:11:00 GMT


Benjamin Bannier reassigned MESOS-8403:

    Assignee: Benjamin Bannier

> Add agent HTTP API operator call to mark local resource providers as gone
> -------------------------------------------------------------------------
>                 Key: MESOS-8403
>                 URL:
>             Project: Mesos
>          Issue Type: Improvement
>          Components: agent, storage
>    Affects Versions: 1.5.0
>            Reporter: Benjamin Bannier
>            Assignee: Benjamin Bannier
>            Priority: Major
>              Labels: mesosphere
> 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.

This message was sent by Atlassian JIRA

View raw message