Time Routed Aliases & CDCR

[Pavel Micka <Pa...@zoomint.com>]

Hello,

We are planning to implement Time Routed Aliases to our solution. But one of our requirements is to be able to provide disaster recovery in case one of two Data Centers dies. We have a network between DCs, which is potentially unstable and has latencies in hundreds of millis.

We were recommended to use CDCR and it really seems to fit our needs. But after reading docs, I have some questions.


1)      With TRA, we define a single solrconfig.xml, this SolrConfig is then assigned to each new collection, when it is automatically created by TRA logic.

a.       BUT CDCR requires us to specify sourceCollectionName and targetCollectionName (https://lucene.apache.org/solr/guide/7_4/cdcr-config.html#cdcr-config), but I can't specify it, because I have the same solrConfig applied to all collections behind the alias. And I do not have the creation of collections in my hands, its done automatically? (and I do not get, why I need to specify the names, when solrconfig.xml file is per collection...)

2)      CDCR docs state that "Configuration files (solrconfig.xml, managed-schema, etc.) are not automatically synchronized between the Source and Target clusters.". Does this apply also to files stored in ZooKeeper? Or only to those on disks. If also to those in ZK, we may have a problem, the collections are created automatically, so we can't easily detect that we should do the ZK sync to backup site.

If there is some smarter way, how to do Disaster Recovery (2 node Solr setup) to backup site (over possibly bad network), please let me know either in this mailing list, or on stack overflow (https://stackoverflow.com/questions/51425009/solrcloud-2-nodes-cluster).

Thanks,

Pavel