David Smiley created SOLR-17153: ----------------------------------- Summary: CloudSolrClient should not throw "Collection not found" with an out-dated ClusterState Key: SOLR-17153 URL: https://issues.apache.org/jira/browse/SOLR-17153 Project: Solr Issue Type: Improvement Security Level: Public (Default Security Level. Issues are Public) Components: SolrJ Reporter: David Smiley
Today, CloudSolrClient will locally fail if it's asked to send a request to a collection that it thinks does not exist due to its local ClusterState view being out-of-date. We shouldn't fail! And most SolrCloud tests should then remove their waitForState calls that follow collection creation! Other stale state matters are out-of-scope. Proposal: CloudSolrClient shouldn't try and be too smart. Always route a request to Solr (any node); don't presume its state is up-to-date. Maybe, after a response is received, it can check if its state has been updated and if not then explicitly get a new state. Or not if that's too complicated. -- This message was sent by Atlassian Jira (v8.20.10#820010) --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org For additional commands, e-mail: issues-h...@solr.apache.org