Hi Kevin, >From what I have gleaned, inter-datacenter Solr replication is not directly supported. Solr Cloud relays each write request to each active node in a shard before returning a response, so the round trip time between your datacenters will be part of the response time for writes.
Using plain old replication between clouds can work, because a cloud collection is basically just a group of ordinary cores working together, but it can be cumbersome to configure and won't work correctly with some mechanisms like failover and near realtime. Current "best practice" is to echo each write to independent clouds in each datacenter. Apparently some thought has gone toward making cloud "rack aware" to better facilitate multi-datacenter setups, but I'm not aware of the progress on that front. Michael Della Bitta Applications Developer o: +1 646 532 3062 | c: +1 917 477 7906 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 w: appinions.com <http://www.appinions.com/> On Mon, Jun 24, 2013 at 12:17 PM, Kevin Osborn <kevin.osb...@cbsi.com>wrote: > We are looking to setup SolrCloud in multiple locations. For now, we will > assume that the data in one center should match the data in another > datacenter. > > Is this the correct type of setup? > > Setup a separate SolrCloud cluster and ZooKeeper quorum in each data > center? Configure cores and collections separately in each data center. And > then use Solr's replication update handler to transfer data from one > datacenter to another? > > Is there any other suggested method that we should investigate? > > -- > *KEVIN OSBORN* > LEAD SOFTWARE ENGINEER > CNET Content Solutions > OFFICE 949.399.8714 > CELL 949.310.4677 SKYPE osbornk > 5 Park Plaza, Suite 600, Irvine, CA 92614 > [image: CNET Content Solutions] >
