[SOLR-11003] Enabling bi-directional CDCR on cluster for better failover

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 7.2
• Component/s: CDCR
• Assignee: Varun Thacker
• Reporter: Amrit Sarkar
• Created: 04/Jul/17 11:23
• Updated: 21/Nov/19 00:42
• Resolved: 06/Nov/17 16:16

Description

The latest version of Solr CDCR across collections / clusters is in active-passive format, where we can index into source collection and the updates gets forwarded to the passive one and vice-versa is not supported.

https://lucene.apache.org/solr/guide/6_6/cross-data-center-replication-cdcr.html
https://issues.apache.org/jira/browse/SOLR-6273

We are try to get a design ready to index in both collections and the updates gets reflected across the collections in real-time (given the backlog of replicating updates to other data center). ClusterACollectionA => ClusterBCollectionB | ClusterBCollectionB => ClusterACollectionA.

The STRONG RECOMMENDED way to keep indexing in ClusterACollectionA which forwards the updates to ClusterBCollectionB. If ClusterACollectionA gets down, we point the indexer and searcher application to ClusterBCollectionB. Once ClusterACollectionA is up, depending on updates count, they will be bootstrapped or forwarded to ClusterACollectionA from ClusterBCollectionB and keep indexing on the ClusterBCollectionB.

Issue Links

• incorporates: SOLR-11412 Documentation changes for SOLR-11003: Bi-directional CDCR support
• relates to: SOLR-9394 CDCR: Exception on target site while using deleteById to delete a document