You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Chun-Hung Hsiao (JIRA)" <ji...@apache.org> on 2018/03/27 23:27:00 UTC

[jira] [Created] (MESOS-8742) Agent resource provider config API calls should be idempotent.

Chun-Hung Hsiao created MESOS-8742:
--------------------------------------

             Summary: Agent resource provider config API calls should be idempotent.
                 Key: MESOS-8742
                 URL: https://issues.apache.org/jira/browse/MESOS-8742
             Project: Mesos
          Issue Type: Bug
            Reporter: Chun-Hung Hsiao
            Assignee: Chun-Hung Hsiao


There are some issues w.r.t. using the current agent resource provider config API calls:

1. {{UPDATE_RESOURCE_PROVIDER_CONFIG}}: If the caller fail to receive the HTTP response code, there is no way to retry the operation without triggering an RP restart.
2. {{ REMOVE_RESOURCE_PROVIDER_CONFIG}}: Due to MESOS-7697, if the caller fail to receive the HTTP response code, a retry will return a 404 Not Found. But due to MESOS-7697, there is no way for the caller to know if the 404 is due to a previous successful config removal or not.

To address these issues, we should make these calls idempotent, such that they return 200 OK when the caller retry. It would be nice if {{ADD_RESOURCE_PROVIDER_CONFIG}} is also idempotent for consistency.



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