[
https://issues.apache.org/jira/browse/MESOS-7697?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16415941#comment-16415941
]
James DeFelice edited comment on MESOS-7697 at 3/27/18 5:13 PM:
----------------------------------------------------------------
[https://github.com/apache/mesos/blob/124c677c86c7b12ca4568f004895b8ca30d60dcf/3rdparty/libprocess/src/process.cpp#L3674]
https://github.com/apache/mesos/blob/master/3rdparty/libprocess/src/process.cpp#L2729-L2740
was (Author: jdef):
https://github.com/apache/mesos/blob/124c677c86c7b12ca4568f004895b8ca30d60dcf/3rdparty/libprocess/src/process.cpp#L3674
> Mesos scheduler v1 HTTP API may generate 404 errors for temporary conditions
> ----------------------------------------------------------------------------
>
> Key: MESOS-7697
> URL: https://issues.apache.org/jira/browse/MESOS-7697
> Project: Mesos
> Issue Type: Bug
> Components: HTTP API, libprocess
> Reporter: James DeFelice
> Priority: Major
> Labels: mesosphere
>
> Returning a 404 error for a condition that's a known temporary condition is
> confusing from a client's perspective. A client wants to know how to recover
> from various error conditions. A 404 error condition should be distinct from
> a "server is not yet ready, but will be shortly" condition (which should
> probably be reported as a 503 "unavailable" error).
> https://github.com/apache/mesos/blob/72752fc6deb8ebcbfbd5448dc599ef3774339d31/src/scheduler/scheduler.cpp#L593
> {code}
> if (response->code == process::http::Status::NOT_FOUND) {
> // This could happen if the master libprocess process has not yet set up
> // HTTP routes.
> LOG(WARNING) << "Received '" << response->status << "' ("
> << response->body << ") for " << call.type();
> return;
> }
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
