Three zookeepers give you bare minimum high availability - one can go down.
But... I would personally assert that running embedded zookeeper is
inherently not "high availability", just by definition (okay, by MY
definition.)
You didn't say whether you were running embedded zookeeper or not.
But if you were, to be HA, your cluster should be able to have all but one
node per shard go down and your cluster should still service both queries
and updates. But with embedded zookeeper on a four-node cluster, taking down
two of the nodes running embedded zookeeper would make zookeeper no longer
usable, and hence your cluster would not be HA.
-- Jack Krupansky
-----Original Message-----
From: Torsten Albrecht
Sent: Wednesday, August 07, 2013 1:15 PM
To: solr-user
Subject: Internal shard communication - performance?
Hi,
I use a system with solr 3 and 20 shards (3 million docs per shard).
At a testsystem with one shard (60 million docs) I get 750 requests per
second. At my live system (20 shards) I get 200 requests per second.
Is the internal communication between the 20 shards a performance killer?
Another question. Is a solr 4 system with solrcloud and Zookeeper a high
availability system?
Regards,
Torsten
