:)
Best,
Alex
--
View this message in context:
http://lucene.472066.n3.nabble.com/SolrCloud-copy-the-index-to-another-cluster-tp4143759p4145517.html
Sent from the Solr - User mailing list archive at Nabble.com.
and run as
primary shards with their own zookeper and then add their own replicas from
the new cluster?
Thank you,
Alex
--
View this message in context:
http://lucene.472066.n3.nabble.com/SolrCloud-copy-the-index-to-another-cluster-tp4143759.html
Sent from the Solr - User mailing list archive
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.
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
Zero read would be enough, we can safely stop index updates for a while. But
have some API endpoints, where read downtime is very undesirable.
Best,
Alex
--
View this message in context:
http://lucene.472066.n3.nabble.com/SolrCloud-copy-the-index-to-another-cluster-tp4143759p4143795.html
Sent
in context:
http://lucene.472066.n3.nabble.com/SolrCloud-copy-the-index-to-another-cluster-tp4143759p4143795.html
Sent from the Solr - User mailing list archive at Nabble.com.