Details
-
Bug
-
Status: Resolved
-
Critical
-
Resolution: Fixed
-
9.7
Description
since solr-17269 the coordinators are not managed by a collection and it's impossible to update their configuration after core creation. (before the change, it was possible to reload the synthetic collection, but not anymore...)
I've been working on solr-17385 trying to add a feature to solr's coordinators, and i'm pretty sure if found a bug
It's relatively easy to recreate: * run 2 solr nodes, one coordinator and one data.
- create a collection on one the data node and add a coordinator to it by running a /select request. you can index a document to make it easyer to see the issue.
- then make a change to your configuration and reload the collection (for example add a costume fl for testing to /select. I added <str name="fl">id,test_s:[value v="test2"]</str>)
- then make a few /select requests from the coordinator and see that the configuration changes are not applied. If you do the same request from the data node it will work as expected
I'm pretty sure it was added in SOLR-17269, there was an improvement made to the coordinator query answering flow that inadvertently lead to a state in which the configuration on the coordinators could never be updated/changed through reload/requests. This happened because it's not verifying it's configuration against the zookeeper anymore after the core has been created, it used to be managed by a synthetic collection but that was removed. But i might be wrong about that.
It's about to be added to solr 9.7, so I hope to save some time and energy for everyone involved by reporting this as early as possible
Attachments
Issue Links
- is caused by
-
SOLR-17269 Don't publish synthetic collection to ZK in solr coordinator nodes
-
- Resolved
-
- links to
