2015-04-28 19:45 GMT+02:00 Erick Erickson :
> I think you're over-thinking the problem though. How often does a
> machine fail? If it's more
> often than once in an blue moon, you have _other_ problems.
My needs are not only high availability (for which 2 nodes would be
enough), but also load bal
Your last comment really answered. A ZK quorum is explicitly ((num zk
instances)/2) + 1.
So no, you don't need 6 nodes at all. It's perfectly reasonable to run
a Solr instance
on each node and a ZK instance (not embedded) on the same three nodes.
I think you're over-thinking the problem though. H
> Yeah, it took me a few tries to get it all straight in my head.
Thanks Erick for your fast answer!
> The only "problem" with running ZK on the same node as Solr is that if the
> node goes down, it takes _both_ zookeeper and Solr with it. If running
> the "embedded zookeeper", then you can't eve
On 4/28/2015 4:40 AM, shacky wrote:
> I'm using Solr for 3 years and now I want to move to a SolrCloud
> configuration on 3 nodes which would make my infrastructure highly
> available.
> But I am very confused about it.
>
> I read that ZooKeeper should not be installed on the same Solr nodes,
> bu
Yeah, it took me a few tries to get it all straight in my head.
Perhaps this will help. Whether or not to install Zookeeper on the same
node as Solr is entirely your decision. And I'm assuming that you're NOT
talking about the embedded Zookeeper BTW.
The only "problem" with running ZK on the same
Hi.
I'm using Solr for 3 years and now I want to move to a SolrCloud
configuration on 3 nodes which would make my infrastructure highly
available.
But I am very confused about it.
I read that ZooKeeper should not be installed on the same Solr nodes,
but I also read another guide that installs one
