Replication should occur on ongoing basis. Sounds interesting. Would wait for the 2014 Solr Revolution videos to be released.
On Tue, Nov 25, 2014 at 10:33 PM, Alexandre Rafalovitch <arafa...@gmail.com> wrote: > Is this one off or on the ongoing bases? > > For ongoing bases, Apple did a presentation at the Solr Revolution and > basically they had a client that would send updates to Solr and the > queue. Then, the other client would read from the queue and apply. > Theirs was bidirectional and symmetric setup, so it was BC/DR. > > Regards. > Alex. > Personal: http://www.outerthoughts.com/ and @arafalov > Solr resources and newsletter: http://www.solr-start.com/ and @solrstart > Solr popularizers community: https://www.linkedin.com/groups?gid=6713853 > > > On 25 November 2014 at 15:29, Gili Nachum <gilinac...@gmail.com> wrote: > > Hi, > > > > > > > > *I need to replicate a collection between SolrClouds, anyone did it?*The > > replication style I need is one direction replicating anything that > happens > > on my main site SolrCloud to the DR site (master->salve) > > > > I considered and decide against synchronizing the collections' shards > > Lucene index over rsync, for being s tricky to arrive at a consistent > index > > and not being efficient enough on bandwidth. > > My current approach is writing a replicator app that knows to sync > between > > two collections, in a fairly generic way, but it's a last of investment > > which I rather avoid. > > > > Saw that master->slave replication can't be used in SolrCloud > > https://cwiki.apache.org/confluence/display/solr/Index+Replication >
