No, you're misunderstanding the setup. Each replica has a complete index. Updates get automatically forwarded to _both_ nodes for a particular shard. So, when a doc comes in to be indexed, it gets sent to the leader for, say, shard1. From there: 1> it gets indexed on the leader 2> it gets forwarded to the replica(s) where it gets indexed locally.
Each replica has a complete index (for that shard). There is no master/slave setup any more. And you do _not_ have to configure replication. Best Erick On Sun, Jul 8, 2012 at 1:03 PM, avenka <ave...@gmail.com> wrote: > I am trying to wrap my head around replication in SolrCloud. I tried the > setup at http://wiki.apache.org/solr/SolrCloud/. I mainly need replication > for high query throughput. The setup at the URL above appears to maintain > just one copy of the index at the primary node (instead of a replicated > index as in a master/slave configuration). Will I still get roughly an > n-fold increase in query throughput with n replicas? And if so, why would > one do master/slave replication with multiple copies of the index at all? > > -- > View this message in context: > http://lucene.472066.n3.nabble.com/SolrCloud-replication-question-tp3993761.html > Sent from the Solr - User mailing list archive at Nabble.com.
