Hi there We have some issues with our solr-cloud setup and the suggester feature.
We run solr 8.8.0 and have three nodes so far. We create collections in an import environment with a local docker solr, where we create a backup and restore the collection on the production system. Along the collection itself we need the suggester index too for our functionality. Since this is not part of the backup/restore we have to build on the production system. And since this is not build on every node automatically we call each node to build it. This already feels wrong but has been working for years by now. We build by calling the api with the following params: 'suggest.build=true','suggest=true', 'q=*:*'.. . The problem is, that some nodes do forward this request, visible by the reponse ( responseHeader.params._forwardedCoung == 1) and so our restore/suggest-build process ends up with having the suggest feature enabled on 2 nodes instead of three. It feels like we do too much workaround and there should be another way. If not, how can we force the suggest build on a node that does not want to? Best Regards Martin Knoller Stocker
