I would think it would be as simple as deleting the update handler from your solrconfig on the search servers
> On Jun 10, 2021, at 6:28 PM, Walter Underwood <[email protected]> wrote: > > What problem are you trying to solve with this? > > Are you trying to send queries to less loaded machines? If so, this won’t do > that. > Leaders only do a little bit more work than followers. All indexing > processing is local > and that is most of the CPU usage. > > wunder > Walter Underwood > [email protected] > http://observer.wunderwood.org/ (my blog) > >> On Jun 10, 2021, at 9:41 AM, Stephen Lewis Bianamara >> <[email protected]> wrote: >> >> Hi Community, >> >> I checked the source and see that this doesn't look to be supported to read >> only from followers. I guess this is possible by pulling the state.json >> data from zookeeper, identifying the leaders, and then passing an explicit >> whitelist not including the leaders. Can someone confirm that this is the >> only way to accomplish this goal? >> >> Thanks, >> Stephen >> >>> On Tue, Jun 8, 2021 at 1:55 PM Stephen Lewis Bianamara < >>> [email protected]> wrote: >>> >>> Hi Folks, >>> >>> Is it possible to configure a Solr cloud to serve reads only from the >>> followers? I see this page >>> <https://solr.apache.org/guide/8_8/distributed-requests.html> explains >>> how to prefer by local, replica type, or sysprops. But is it possible to >>> specify that something should be served by a non-leader whenever possible >>> (or even require it to return at all)? E.g., something like >>> >>> shards.preference=leader:false >>> >>> >>> Thanks, >>> Stephen >>> >
