Erick Erickson created SOLR-10517:
-------------------------------------
Summary: It would be nice to have a way to insure that config and
schema API calls have propagated to all cores
Key: SOLR-10517
URL: https://issues.apache.org/jira/browse/SOLR-10517
Project: Solr
Issue Type: Improvement
Security Level: Public (Default Security Level. Issues are Public)
Affects Versions: 6.5, master (7.0)
Reporter: Erick Erickson
While working on SOLR-10493 I discovered that the test was failing because a
config change had been made. That test goes on to delete collections, but the
config change is still sending out reload commands. The sequence is something
like this:
1> config change request is made.
2> call returns, but various core reload commands are still being sent out
3> collection is deleted
4> one of the reloads from <2> arrives
Test fails because the core (and descriptor) is gone.
This was succeeding before SOLR-10007 because (I think) there was a copy of the
coreDescriptor being held in several places and one of the un-deleted ones was
being used.
It would be good if there were a way to be sure that that config and schema
calls had been propagated to all replicas in all affected collections.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
