No, don't disable replication! The way shards ordinarily keep up with updates is by sending every document to each member of the shard. However, if a shard goes offline for a period of time and comes back, replication is used to "catch up" that shard. So you really need it on.
If you created your collection with the collections API and the required bits are in schema.xml and solrconfig.xml, you should be good to go. See https://wiki.apache.org/solr/SolrCloud#Required_Config Michael Della Bitta Applications Developer o: +1 646 532 3062 appinions inc. "The Science of Influence Marketing" 18 East 41st Street New York, NY 10017 t: @appinions <https://twitter.com/Appinions> | g+: plus.google.com/appinions<https://plus.google.com/u/0/b/112002776285509593336/112002776285509593336/posts> w: appinions.com <http://www.appinions.com/> On Tue, Mar 25, 2014 at 12:42 PM, Software Dev <static.void....@gmail.com>wrote: > I see that by default in SolrCloud that my collections are > replicating. Should this be disabled in SolrCloud as this is already > handled by it? > > From the documentation: > > "The Replication screen shows you the current replication state for > the named core you have specified. In Solr, replication is for the > index only. SolrCloud has supplanted much of this functionality, but > if you are still using index replication, you can use this screen to > see the replication state:" > > I just want to make sure before I disable it that if we send an update > to one server that the document will be correctly replicated across > all nodes. Thanks >
