Hello Saksham
1. I meant the later (client/code) level. I suppose it might be manipulated
via runtime properties. Right, it's enough hassle.
2. I never heard of making a replica inactive as well as informing Solr
about absence of update.
If you can make replica inactive for queries (a kind of shar
Hi Mikhail,
Thanks for the response.
*1. How to maintain shards.preference parameter?* According to my
understanding we can maintain shards.preference information at either solr
level or at code level, both of which have downsides to them. If
shards.pref is maintained at solr level we will need to
Hello Saksham.
I think there's no quick answer for this.
a client can add this parameter to exclude a node from querying.
shards.preference=replica.location:http://server1,replica.location:
http://server2
But what can really stop shard queries is dropping replicas:
https://solr.apache.org/guide/sol
Hi,
Is there a way of automwarming solr cores/shards before adding them to the
solr cloud cluster?
We are using solr cloud with a cluster of 8 nodes where each node consists
of 1 shard of a collection. It is very troublesome to restart a solr node
for some maintenance activity as it leads to mult
