[
https://issues.apache.org/jira/browse/MESOS-8403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16602138#comment-16602138
]
Benjamin Bannier commented on MESOS-8403:
-----------------------------------------
{noformat}
commit 6a98857cf429580b72cd97ddd749a074c3e4524d
Author: Benjamin Bannier <[email protected]>
Date: Mon Aug 13 11:10:59 2018 +0200
Sent an event to resource providers when they are removed.
In order to allow proper cleanup the resource provider manager sends a
`REMOVED` to a resource provider when it is being removed.
The event is not sent reliably, i.e., if the resource provider was
e.g., not subscribed when it was removed we currently will never
attempt to resend the event.
Review: https://reviews.apache.org/r/68145/
commit 75bc091e123744003f2ef956be54ad7f562c4815
Author: Benjamin Bannier <[email protected]>
Date: Wed Aug 15 09:37:12 2018 +0200
Made RP manager only send resource provider ID on state updates.
With the introduction of the resource provider `SUBSCRIBE` event which
contains the full `ResourceProviderInfo` of a subscribed resource
provider, we can avoid sending the `ResourceProviderInfo` in
`UPDATE_STATE` events and instead only send a `ResourceProviderID`
like in most other messages.
Review: https://reviews.apache.org/r/68362
commit f83b31867c86e35f38fd538993138768939291f0
Author: Benjamin Bannier <[email protected]>
Date: Mon Aug 13 11:11:04 2018 +0200
Added actions and ACLs to authorize removal of resource providers.
Review: https://reviews.apache.org/r/68146/
commit 4b558e24594b43456f35de697ed8484bbb331fe1
Author: Benjamin Bannier <[email protected]>
Date: Mon Aug 13 11:10:51 2018 +0200
Added methods to remove resource providers from provider manager.
This patch adds a method to remove a resource provider from the
resource provider manager. The resource provider will be marked as
removed in the manager's registry and disconnected. We also expose a
new `REMOVE` event whenever a resource provider was removed.
This patch does not add integration with e.g., the agent.
Review: https://reviews.apache.org/r/68144/
commit 700a62313e8f0fce94f43c9be6f54fc848cf6eb5
Author: Benjamin Bannier <[email protected]>
Date: Mon Aug 13 11:10:44 2018 +0200
Made resource provider manager emit an event when provider subscribed.
This patch adds a `SUBSCRIBE` resource provider message which is
emitted by the resource provider manager when a resource provider
subscribes. This event can e.g., be used to detect subscriptions when
theresource provider never updates any resources.
We currently do not expose this event from the agent outwards.
Review: https://reviews.apache.org/r/68143/
commit 701e014a69b1f692f011e79169582c701ebf4f3c
Author: Benjamin Bannier <[email protected]>
Date: Fri Aug 17 12:00:43 2018 +0200
Allowed tracking of resource providers w/o resource version in agent.
This will be used in a later patch introducing explicit handling of
resource provider subscription events in the agent.
Review: https://reviews.apache.org/r/68407
{noformat}
> 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)
