+1, albeit this is super sad to call waitForState all over the place. IMO
it's a fundamental flaw that CloudSolrClient is not 100% reliable to
interact with a collection immediately after creating it, using the same
client instance. IMO even another client should work as well -- don't see
it, dou
Just a general question to us all -- do we want to create bespoke
interfaces for lifecycle or maybe embrace something else? Like Jetty's or
maybe HK2 (used by Jersey)? Not sure if this quite makes sense; I haven't
thought through the practicalities.
On Sat, Oct 12, 2024 at 11:07 PM Gus Heck wro
Recently, a common exception
(org.apache.lucene.store.AlreadyClosedException: this Directory is closed)
seen in multiple failed test cases.
FAILED: org.apache.solr.cloud.TestPullReplica.testKillPullReplica
FAILED:
org.apache.solr.cloud.SplitShardWithNodeRoleTest.testSolrClusterWithNodeRoleWithPu
