mesos-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Neil Conway (JIRA)" <>
Subject [jira] [Updated] (MESOS-4421) Document that /reserve, /create-volumes endpoints can return misleading "success"
Date Wed, 20 Jan 2016 00:17:39 GMT


Neil Conway updated MESOS-4421:
          Sprint: Mesosphere Sprint 27
    Story Points: 3

> Document that /reserve, /create-volumes endpoints can return misleading "success"
> ---------------------------------------------------------------------------------
>                 Key: MESOS-4421
>                 URL:
>             Project: Mesos
>          Issue Type: Task
>          Components: documentation, master
>            Reporter: Neil Conway
>            Assignee: Neil Conway
>              Labels: documentation, endpoint, mesosphere, persistent-volumes, reservations
> The docs for the {{/reserve}} endpoint say:
> {noformat}
> 200 OK: Success (the requested resources have been reserved).
> {noformat}
> This is not true: the master returns {{200}} when the request has been validated and
a {{CheckpointResourcesMessage}} has been sent to the agent, but the master does not attempt
to verify that the message has been received or that the agent successfully checkpointed.
Same behavior applies to {{/unreserve}}, {{/create-volumes}}, and {{/destroy-volumes}}.
> We should _either_:
> 1. Accurately document what {{200}} return code means.
> 2. Change the implementation to wait for the agent's next checkpoint to succeed (and
to include the effect of the operation) before returning success to the HTTP client.

This message was sent by Atlassian JIRA

View raw message