Hi,
524 or 504 both refer to timeouts, but both are meant for proxies (so
reverse proxy can't reach the backend server in time). So both of them
do not match.
408 is "request timeout", but that's client's fault (4xx code). In that
case its a more technical code because it also requires to close the
connection and not keep it alive, so we can't trigger that from Servlet
API in a correct way.
503 does not fit well as Solr is not overloaded, but would be the only
alternative I see. Maybe add a new Solr-specific one? Anyways, I think
500 seems the best response unless you find another one not proxy-related.
Uwe
Am 18.03.2024 um 23:23 schrieb David Smiley:
If timeAllowed is set and Solr takes too long then we fail the
response with an HTTP 500 response code. It's not bad but it's not
ideal IMO because Solr's health could reasonably be judged by looking
for 500's specifically as a sign of a general error that service
operators should pay attention to. There is a 529 response code used
by CloudFlare (judging from Wikipedia):
https://en.wikipedia.org/wiki/List_of_HTTP_status_codes
Any opinion on the use of 529 instead of 500; or alternative perspectives?
~ David Smiley
Apache Lucene/Solr Search Developer
http://www.linkedin.com/in/davidwsmiley
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@solr.apache.org
For additional commands, e-mail: dev-h...@solr.apache.org
--
Uwe Schindler
Achterdiek 19, D-28357 Bremen
https://www.thetaphi.de
eMail: u...@thetaphi.de
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@solr.apache.org
For additional commands, e-mail: dev-h...@solr.apache.org
