Description
SOLR-12999 introduced a new behavior where Solr nodes can now know to quickly reject requests when the index is unavailable due to a full IndexFetch from the master/leader - but when this change was implemented it was done soe using the HTTP status code "403" (Forbidden) which semantically indicates a client error and carries with it the understanding that the client should not re-attempt the request ... at least not w/o modification (typically adding authentication information)
A more semantically correct response code would be 503 (Service Unavailable) which indicates a server problem (that may be resolved at some point in the future) and clients would not be ill-behaved to try again later.
returning 503 in this particular code path would also be more consistent with other places in the solr code based where nodes respond with "503" when they are "not currently ready for requests" (but might be soon)
Attachments
Issue Links
- is part of
-
SOLR-13474 Fix "Search is temporarily disabled" logic to be consistent for entire request
-
- Closed
-
- is related to
-
SOLR-12999 Index replication could delete segments first
-
- Resolved
-