Erick,
thanks a lot, very clear.
Reinaldo
On Thu, Jun 4, 2020 at 8:37 PM Erick Erickson
wrote:
> Close. Zookeeper is not involved in routing requests. Each Solr node
> queries Zookeeper to get the topology of the cluster, and thereafter
> Zookeeper will notify each node when the topology change
Close. Zookeeper is not involved in routing requests. Each Solr node
queries Zookeeper to get the topology of the cluster, and thereafter
Zookeeper will notify each node when the topology changes, i.e.
a node goes up or down, a replica goes into recovery etc. Zookeeper
does _not_ get involved in ea
Erick,
thanks for the reply.
Your last line puzzled me a bit. You wrote
*"The theory is that all the top-level requests shouldn’t be handled by the
same Solr instance if a client is directly using the http address of a
single node in the cluster for all requests."*
We are using 2 machines (2 diffe
The base algorithm for searches picks out one replica from each
shard in a round-robin fashion, without regard to whether it’s on
the same machine or not.
You can alter this behavior, see:
https://lucene.apache.org/solr/guide/8_1/distributed-requests.html
When you say “the exact same search”, i
Hi,
I have a question regarding solrcloud searches on both replicas of an index.
I have a solrcloud setup with 2 physical machines (let's call them A and
B), and my index is divided into 2 shards, and 2 replicas, such that each
machine has a full copy of the index. My Zookeeper setup uses 3 instan
