[jira] [Comment Edited] (MESOS-8403) Add agent HTTP API operator call to mark local resource providers as gone

["Benjamin Bannier (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/MESOS-8403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16565525#comment-16565525 ] 

Benjamin Bannier edited comment on MESOS-8403 at 10/25/18 10:47 AM:
--------------------------------------------------------------------

Reviews:

-[https://reviews.apache.org/r/68143/]-
 -[https://reviews.apache.org/r/68144/]-
 -[https://reviews.apache.org/r/68146/]-
 [https://reviews.apache.org/r/68147/]
https://reviews.apache.org/r/69158/
https://reviews.apache.org/r/69158/


was (Author: bbannier):
Reviews:

-[https://reviews.apache.org/r/68143/]-
 -[https://reviews.apache.org/r/68144/]-
 -[https://reviews.apache.org/r/68146/]-
 [https://reviews.apache.org/r/68147/]

> Add agent HTTP API operator call to mark local resource providers as gone
> -------------------------------------------------------------------------
>
>                 Key: MESOS-8403
>                 URL: https://issues.apache.org/jira/browse/MESOS-8403
>             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
(v7.6.3#76005)