You want external zookeepers. Partially because you don't want your Solr
garbage collections holding up zookeeper availability, but also because
you don't want your zookeepers going offline if you have to restart Solr
for some reason.
Also, you want 3 or 5 zookeeepers, not 4 or 8.
On 10/27/14 10:35, Bernd Fehling wrote:
While starting now with SolrCloud I tried to understand the sense
of external zookeeper.
Let's assume I want to split 1 huge collection accross 4 server.
My straight forward idea is to setup a cloud with 4 shards (one
on each server) and also have a replication of the shard on another
server.
server_1: shard_1, shard_replication_4
server_2: shard_2, shard_replication_1
server_3: shard_3, shard_replication_2
server_4: shard_4, shard_replication_3
In this configuration I always have all 4 shards available if
one server fails.
But now to zookeeper. I would start the internal zookeeper for
all shards including replicas. Does this make sense?
Or I only start the internal zookeeper for shard 1 to 4 but not
the replicas. Should be good enough, one server can fail, or not?
Or I follow the recommendations and install on all 4 server
an external seperate zookeeper, but what is the advantage against
having the internal zookeeper on each server?
I really don't get it at this point. Can anyone help me here?
Regards
Bernd
