FTS sets errors codes in the HTTP response header already as of 6.5 (which needs to documented).
Here's details ..
FTS error status |
Error description |
HTTP response status code |
HTTP response status description |
success |
Query was processed successfully |
200 |
OK |
query request rejected |
Seen when the FTS throttler rejects the query due to high memory usage |
429 |
Too Many Requests |
authentication failure |
Seen when the auth credentials provided do not qualify. |
403 |
Forbidden |
malformed query request |
Seen when the search request JSON isn't an recognized format |
400 |
Bad Request |
internal failure |
Seen when FTS is unable to fetch any necessary data for responding to the request |
500 |
Internal Server Error |
page not found |
When the endpoint for the request doesn't exist |
404 |
Not Found |
pre condition failed |
When a pre-condition (like a consistency error) has occurred |
412 |
Precondition Failed |
context deadline exceeded |
Seen when FTS fails to respond to the request within the set timeout period |
- |
- |
For when FTS fails to respond to the request within the set the timeout period, you'd see a message in the search result like this ..
"status": {
|
"total": 6,
|
"failed": 6,
|
"successful": 0,
|
"errors": {
|
"travel_5563340761e0e2a7_13aa53f3": "context deadline exceeded",
|
"travel_5563340761e0e2a7_18572d87": "context deadline exceeded",
|
"travel_5563340761e0e2a7_54820232": "context deadline exceeded",
|
"travel_5563340761e0e2a7_6ddbfb54": "context deadline exceeded",
|
"travel_5563340761e0e2a7_aa574717": "context deadline exceeded",
|
"travel_5563340761e0e2a7_f4e0a48a": "context deadline exceeded"
|
}
|
},
|
However, the HTTP response code isn't set (in the above situation) as the response header is sent immediately and FTS fails to get results to put in the response body within the specified time frame - which is when the above response snippet is sent.
FTS sets errors codes in the HTTP response header already as of 6.5 (which needs to documented).
Here's details ..
For when FTS fails to respond to the request within the set the timeout period, you'd see a message in the search result like this ..
}
},
However, the HTTP response code isn't set (in the above situation) as the response header is sent immediately and FTS fails to get results to put in the response body within the specified time frame - which is when the above response snippet is sent.