Re: [PR] SOLR-17153: CloudSolrClient should not throw "Collection not found" with an out-dated ClusterState [solr]

["dsmiley (via GitHub)" <gi...@apache.org>]

dsmiley commented on PR #2363:
URL: https://github.com/apache/solr/pull/2363#issuecomment-2030147402

   Maybe in this PR or another we'll add a test like you (Mark) describe to ensure that CloudSolrClient directs requests to Solr in all circumstances (giving up on smart routing to a core if this can't be determined) so long as we have confirmed the collection in fact exists (which again requires talking to the backend).  My concern is that, as we saw here before the changes, CloudSolrClient would yield an error prematurely.
   
   Hmmm; I wonder what the state.json looks like at each incremental step of a trivial one-shard 2-replica collection.  Something to investigate.  If it's a bit incremental; it'd be cool if Solr might be improved to get the collection to exist with at least a core in one-shot, thus eliminating the possibility a Solr node having a collection's state that is so partial that it can't even route a request to it.
   
   It'd be nice to remove so many waitForState's but maybe we can't in good conscience.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscribe@solr.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@solr.apache.org
For additional commands, e-mail: issues-help@solr.apache.org