I¹ve been working on this tool, which wraps the collections API to do more advanced cluster-management operations: https://github.com/whitepages/solrcloud_manager
One of the operations I¹ve added (copy) is a deployment mechanism that uses the replication handler¹s snap puller to hot-load a pre-indexed collection from one solrcloud cluster into another. You create the same collection name with the same shard count in two clusters, index into one, and copy from that into the other. This method won¹t work as a method of active replication, since it copies the whole index. If you only need a periodic copy between data centers though, or want someplace to restore from in case of critical failure (until you can properly rebuild), there might be something you can use here. On 8/19/14, 12:45 PM, "reparker23" <reparke...@gmail.com> wrote: >Are there any more OOB solutions for inter-SolrCloud replication now? Our >indexing is so slow that we cannot rely on a complete re-index of data >from >our DB of record (SQL) to recover data in the Solr indices. > > > >-- >View this message in context: >http://lucene.472066.n3.nabble.com/Replicating-Between-Solr-Clouds-tp41211 >96p4153856.html >Sent from the Solr - User mailing list archive at Nabble.com.
