503 Service Unavailable is the standard response for down or overloaded. I don’t see that 529 is significantly different.
I do think it is a good idea to distinguish overload or down conditions from the catch-all 500 error. I interpret that as a broken server, not one that is functioning properly but overloaded. wunder Walter Underwood wun...@wunderwood.org http://observer.wunderwood.org/ (my blog) > On Mar 18, 2024, at 3:23 PM, David Smiley <dsmi...@apache.org> wrote: > > 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
