I'm currently playing around with Solr Cloud migration strategies, too. I'm wondering... when you say "zero downtime," do you mean zero *read* downtime, or zero downtime altogether?
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, Jun 24, 2014 at 1:43 PM, heaven <aheave...@gmail.com> wrote: > I've just realized that old and new clusters do use different > installations, > configs and lib paths. So the nodes from the new cluster will probably > simply refuse to start using configs from the old zookeper. > > Only if there is a way to run them with their own zookeper and then > manually > add as replicas to the old cluster, so old and new clusters keep using > their > own zookepers. > > > > -- > View this message in context: > http://lucene.472066.n3.nabble.com/SolrCloud-copy-the-index-to-another-cluster-tp4143759p4143769.html > Sent from the Solr - User mailing list archive at Nabble.com. >
