Hi, > Don't run multiple instances of Solr on one machine. Instead, run one > instance per machine and create the collection with the maxShardsPerNode > parameter set to 2 or whatever value you need.
Ok. > Yet another whole separate discussion: You need three physical nodes for > a redundant zookeeper, but I see only one host (localhost) in your > zkHost parameter. I know, but thanks for pointing it out. At the moment I’m doing a proof of concept investigating SolrCloud. Properly configuring Zookeeper comes later. > The way you've set it up, SolrCloud just sees that you have four Solr > instances. It does not know that they are on the same machine. As far > as it is concerned, they are entirely separate. > > Something that would be a good idea is an optional config flag that > would make SolrCloud compare hostnames when building a collection and > avoid putting replicas on nodes where the hostname matches. Whether to > default this option to on or off is a whole separate discussion. That would be a great addition. Because as of now I don’t see a way of having a reproducible failover mechanism without additional physical machines. Or am I wrong here? Let’s say I have two leaders (host1, and host2) running, each with one shard of the collection running. How can I make sure that host1 will run a replica of host2 ? Thanks Oliver