[
https://issues.apache.org/jira/browse/SOLR-13469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hoss Man resolved SOLR-13469.
-----------------------------
Resolution: Fixed
Assignee: Hoss Man
Fix Version/s: 8.2
master (9.0)
> rejected requests during ful IndexFetch should not use 403 response code
> ------------------------------------------------------------------------
>
> Key: SOLR-13469
> URL: https://issues.apache.org/jira/browse/SOLR-13469
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: Hoss Man
> Assignee: Hoss Man
> Priority: Major
> Fix For: master (9.0), 8.2
>
>
> 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)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
