A single zookeeper node could be a single point of failure. It is
recommended that you have at least one three zookeeper nodes running as
an ensemble.
Zookeeper has a simple rule - over half of your nodes must be available
to achieve quorum and thus be functioning. This is to avoid
'split-brain'.
OK, got it. Thanks.
On 19 November 2012 15:00, Mark Miller wrote:
> Nodes stop accepting updates if they cannot talk to Zookeeper, so the
> external load balancer is no advantage there.
>
> CloudSolrServer will be smart about knowing who the leaders are,
> eventually will do hashing, will auto a
Nodes stop accepting updates if they cannot talk to Zookeeper, so the external
load balancer is no advantage there.
CloudSolrServer will be smart about knowing who the leaders are, eventually
will do hashing, will auto add/remove nodes from rotation based on the cluster
state in Zookeeper, and
Hi,
As far as I know CloudSolrServer is recommended to be used for indexing to
SolrCloud. I wonder what are advantages of this approach over external
load-balancer ? Let's say I have 4 nodes SolrCloud (2 shards + replicas) +
1 server running ZooKeeper. I can use CloudSolrServer for indexing or use
