It depends on how you create your collection. If you want to pre configure your collection in solr.xml (collection1 comes this way), then everything depends on what you set for numShards on startup.
If you wanted to have one collection across 4 nodes with 2 shards, each shard with 1 leader and 1 replica, you would simply startup 4 nodes with numShards=2 set on each of them (only the first matters, but to avoid races you can pass it to each). Since it knows you want two shards, all Solr nodes started that are configured with SolrCore's part of your collection will automatically join one of the two shards as replicas. So to summarize - it's totally determined by the numShards startup system property. If you are using the Collections API to create your collection, you can explicitly specify the replicationFactor as well as numShards. In this case, the replicationFactor you pass will limit how many replicas are created to the given value. This is so that, even if you have 100 nodes, you can create new collections that span 10, or 20 nodes, rather than using every node that is available. - Mark On Oct 18, 2012, at 8:12 PM, balaji.gandhi <balaji.gan...@apollogrp.edu> wrote: > Hi Team, > > We are trying to configure replicationFactor in SolrCloud mode to specify a > minimum number of replicas in the cluster. > > We know that if (number of nodes) = 2 * (number of shards) Solr takes care > of the replication. > > Is there a way to force the replicationFactor when (number of nodes) < 2 * > (number of shards)? > > Looking to setup something like the below from SolrCloud wiki:- > http://people.apache.org/~markrmiller/2shard4server2.jpg > <http://people.apache.org/~markrmiller/2shard4server2.jpg> > > Thanks, > Balaji > > > > -- > View this message in context: > http://lucene.472066.n3.nabble.com/SolrCloud-Configuring-replicationFactor-tp4014625.html > Sent from the Solr - User mailing list archive at Nabble.com.
