[
https://issues.apache.org/jira/browse/SOLR-9664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18132157#comment-18132157
]
Nick Shanin commented on SOLR-9664:
-----------------------------------
>From code reading against apache/main b73f03976fa, a _route_ query from a
>stale client cache is caught by the server's stateVer check
>(solr/core/src/java/org/apache/solr/servlet/HttpSolrCall.java:846-866), and
>the client re-fetches and retries
>(solr/solrj/src/java/org/apache/solr/client/solrj/impl/CloudSolrClient.java:830-832).
> Reading finds no silent miss on main. Is closure OK?
🤖 AI-generated 🤖
> CloudSolrClient's cluster state cache can break query routing for new shards
> ----------------------------------------------------------------------------
>
> Key: SOLR-9664
> URL: https://issues.apache.org/jira/browse/SOLR-9664
> Project: Solr
> Issue Type: Bug
> Affects Versions: 6.3
> Reporter: Alan Woodward
> Priority: Major
> Attachments: SOLR-9664.patch
>
>
> CloudSolrClient can do query routing if a query has an explicit route
> parameter set on it. This doesn't play well with the cluster state cache,
> however, because the routing is done entirely client-side, with no
> opportunity for a node to report that the cache is out-of-date.
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
