Not at all. ZooKeeper is just the record-keeper for the _states_ of the replicas, i.e. whether they are active, recovering, down and the like, as well as the config sets (schema, solrconfig.xml etc).
There is no relationship between these two counts. Well, if you have a zillion collections with a zillion replicas you may want to partition things, but I've seen 100K replicas hosted on 3 ZK nodes. And a misconception you have is the shard/replica usage. Replicas exist for two reasons: 1> HA. If a replica goes down, the other replicas pick up the load 2> increasing QPS. If I have 5 replicas/shard and can serve X QPS, increasing to 10 replicas/shard should give me close to 2X QPS . _Shards_ only come in to play when you want to have more documents than you can comfortably fit in a one-shard (perhaps many replicas) setup. Best, Erick On Fri, Jun 8, 2018 at 11:13 AM, THADC <timothy.clotworthy.j...@gmail.com> wrote: > Hello, > > I am having trouble getting a clear understanding of the relationship > between my 3-node zookeeper cluster and how those 3 nodes relate to solr > replicas (if at all). Since the replicas exist for failover purposes > (correct?) as opposed to for load balancing (which is what the sharding > strategy addresses), I was assuming that there should be as many replicas > per shard as there are zookeeper nodes. So in my case, one zookeeper node is > the leader for a given shard, while the other two are followers. Is this > correct? > > Any insights are appreciated. thanks! > > > > -- > Sent from: http://lucene.472066.n3.nabble.com/Solr-User-f472068.html
