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

Chun-Hung Hsiao commented on MESOS-9228:
----------------------------------------

Backported to 1.7.x:
{noformat}
commit 86bd9e4c5b5c0d807bbbe54e10e53f389cd7a7ec
Author: Chun-Hung Hsiao <[email protected]>
Date: Tue Sep 18 12:59:52 2018 -0700

Removed unnecessary failure handling in agent HTTP API handlers.

The current agent HTTP API handlers either unnecessarily handle failures
on always-ready futures, or return "500 Internal Server Error"
unnecessarily. This patch removes those unnecessarily code.

Review: https://reviews.apache.org/r/68755{noformat}
{noformat}
commit 84fa09e3a7a807edce7c0655622e0662ac97031d
Author: Chun-Hung Hsiao <[email protected]>
Date: Tue Sep 18 14:40:55 2018 -0700

Performed RP-specific validations when adding/updating RP configs.

Each type of RP might have some specific validations for RP info. For
example, SLRP requires the `storage` field to be set. This patch makes
the local RP daemon to perform such validations when adding/updating
configs, so the `ADD_RESOURCE_PROVIDER_CONFIG` and
`UPDATE_RESOURCE_PROVIDER_CONFIG` calls can fail fast.

Review: https://reviews.apache.org/r/68756{noformat}
{noformat}
commit 76bc3efe4822f285a6783170ba2c12e3546aec35
Author: Chun-Hung Hsiao <[email protected]>
Date: Thu Sep 20 11:25:11 2018 -0700

Moved the container ID prefix generation to `LocalResourceProvider`.

It is more reasonable to not allow each specific resource provider to
construct their own container ID prefix, otherwise it would be hard to
avoid conflicts. Therefore we now established the convension of how the
prefix is constructed in `LocalResourceProvider`.

Review: https://reviews.apache.org/r/68790{noformat}
{noformat}
commit 39e6911567517689452be23893f9031fb02ceebf
Author: Chun-Hung Hsiao <[email protected]>
Date: Thu Sep 20 15:06:51 2018 -0700

Cleaned up residual containers when removing resource provider configs.

When processing `REMOVE_RESOURCE_PROVIDER_CONFIG`, the local resource
provider daemon now performs a best-effort cleanup by killing all
standalone containers prefixed by the 'cid_prefix' of the resource
provider. During the cleanup, no resource provider config with the same
type and name can be added.

Review: https://reviews.apache.org/r/68763{noformat}

> SLRP does not clean up plugin containers after it is removed.
> -------------------------------------------------------------
>
>                 Key: MESOS-9228
>                 URL: https://issues.apache.org/jira/browse/MESOS-9228
>             Project: Mesos
>          Issue Type: Bug
>          Components: storage
>    Affects Versions: 1.5.0, 1.6.0, 1.7.0
>            Reporter: Chun-Hung Hsiao
>            Assignee: Chun-Hung Hsiao
>            Priority: Blocker
>              Labels: mesosphere, storage
>             Fix For: 1.7.1, 1.8.0
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to