mesos-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Neil Conway (JIRA)" <>
Subject [jira] [Created] (MESOS-3920) Considering changing /reserve, /unreserve endpoint syntax
Date Fri, 13 Nov 2015 19:10:10 GMT
Neil Conway created MESOS-3920:

             Summary: Considering changing /reserve, /unreserve endpoint syntax
                 Key: MESOS-3920
             Project: Mesos
          Issue Type: Bug
            Reporter: Neil Conway
            Priority: Minor

Right now, the "reserve" and "unreserve" endpoints work as follows:

1. slaveID is sent as a separate query parameter
2. the resources to reserve are sent as the "reserve" query parameter, where the value is
encoded in JSON

This is weird, for two reasons:

1. It is more typical for POST to send the content of the new document in the request body,
not as parameters to the query string (e.g.,
2. It is weird to mix query parameters (slaveID, resources) with JSON-encoded values. Why
not just post a single JSON document with all the information required for a dynamic reservation?

Obviously, there are some backward compatibility concerns if we want to change this.

This message was sent by Atlassian JIRA

View raw message