David Smiley created SOLR-17601:
-----------------------------------
Summary: HttpSolrCall: INVALID_STATE: use an HTTP response header
instead
Key: SOLR-17601
URL: https://issues.apache.org/jira/browse/SOLR-17601
Project: Solr
Issue Type: Improvement
Components: SolrCloud, SolrJ
Reporter: David Smiley
CloudSolrClient & Solr (HttpSolrCall, specifically) work together so that
CloudSolrClient knows the collection's client-side cached state is out-of-date.
But the state version is appended to the payload of the response from Solr,
which CloudSolrClient removes (awkward). Furthermore if HttpSolrCall realizes
it needs to proxy the request to another node, it can't (using this strategy)
so it fails the request with HTTP 510 which CloudSolrClient understands. If
that request was retry-able, the client won't know but requests like indexing
are not and so the client sees the error.
I propose using an HTTP response header to have the state version, and to
always supply it from SolrCloud instead of only when a request parameter is
passed.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
