[
https://issues.apache.org/jira/browse/MESOS-2205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14360103#comment-14360103
]
Nikita Vetoshkin commented on MESOS-2205:
-----------------------------------------
Other codes that come to mind are:
* {{400 Bad Request}} for invalid arguments.
* {{412 Precondition Failed}}
I think that {{409 Conflict}} should be used for something like concurrent
update issue, when someone already modified item you wish to update. Mesos
example that comes to mind is attempt to {{launchTasks}} with optimistic offers.
I like the way errors are specified in grpc, e.g. here is [Java
version|https://github.com/grpc/grpc-java/blob/master/core/src/main/java/io/grpc/Status.java#L130].
In our case we are interested in {{INVALID_ARGUMENT}}, {{FAILED_PRECONDITION}}
and {{OUT_OF_RANGE}}.
Anyway, HTTP codes are not strict and can be argued about which to choose.
Specifying which code was chosen for which case is a must :)
> Add user documentation for reservations
> ---------------------------------------
>
> Key: MESOS-2205
> URL: https://issues.apache.org/jira/browse/MESOS-2205
> Project: Mesos
> Issue Type: Documentation
> Components: documentation, framework
> Reporter: Michael Park
> Assignee: Michael Park
> Labels: mesosphere
>
> Add a user guide for reservations which describes basic usage of them, how
> ACLs are used to specify who can unreserve whose resources, and few advanced
> usage cases.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
