Thanks mark !
On Sun, Nov 11, 2012 at 5:46 PM, Mark Miller wrote:
> When SolrCloud is in a steady state (eg the number of nodes in the cluster
> is not changing and config is not changing), Solr does not really talk to
> ZooKeeper other than really light stuff like a heartbeat and maintaining a
When SolrCloud is in a steady state (eg the number of nodes in the
cluster is not changing and config is not changing), Solr does not
really talk to ZooKeeper other than really light stuff like a heartbeat
and maintaining a connection. So performance is not likely a large
concern here.
Mostly
let me see if i get this correctly,
greater the no.of zookeeper nodes , more the time it takes to come to a
consensus.
During an indexing operation, how many times does a solr client needs to
contact zookeeper for consensus ?
- per docs ? per commit ? ?
thanks,
Ani
On Sun, Nov 11, 2012 at 11:1
Thanks, Jack, this is a great explanation! And since a greater number
of ZK nodes tends to degrade write performance, that would be a factor
in making every Solr node a ZK node as well. Much obliged!
Nick
On 11/11/2012 10:45 AM, Jack Krupansky wrote:
"Production" typically implies "hi
"Production" typically implies "high availability" and in a distributed
system the goal is that the overall cluster integrity and performance should
not be compromised just because a few "worker" nodes go down. Solr nodes do
a lot of complex operations and are quite prone to running into "issues
