I guess you can do this by switching off the source data center, but you would
need to look more in your architecture and especially applications that use
solr to verify this.
It may look easy but I would test it before.
> Am 06.06.2019 um 17:24 schrieb Joe Lerner :
>
> Ooohh...interesting. Th
Ooohh...interesting. Then, presumably there is some way to have what was the
cross-data-center replica become the new "primary"?
It's getting too easy!
Joe
--
Sent from: http://lucene.472066.n3.nabble.com/Solr-User-f472068.html
An alternative to backup and restore could be the data center replication in
Solr:
https://lucene.apache.org/solr/guide/7_3/cross-data-center-replication-cdcr.html
> Am 05.06.2019 um 19:18 schrieb Joe Lerner :
>
> Hi,
>
> Our application is migrating from on-premise to AWS. We are currently on
On 6/5/2019 11:18 AM, Joe Lerner wrote:
Our application is migrating from on-premise to AWS. We are currently on
Solr Cloud 7.3.0.
We are interested in exploring ways to do this with minimal, down-time, as
in, maybe one hour.
One strategy would be to set up a new empty Solr Cloud instance in A
Hi,
Our application is migrating from on-premise to AWS. We are currently on
Solr Cloud 7.3.0.
We are interested in exploring ways to do this with minimal, down-time, as
in, maybe one hour.
One strategy would be to set up a new empty Solr Cloud instance in AWS, and
reindex the world. But reinde
