[
https://issues.apache.org/jira/browse/SOLR-11003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16073586#comment-16073586
]
Amrit Sarkar commented on SOLR-11003:
-------------------------------------
Patch uploaded:
{code}
modified:
solr/core/src/java/org/apache/solr/handler/CdcrReplicator.java
modified:
solr/core/src/java/org/apache/solr/update/CdcrTransactionLog.java
modified:
solr/core/src/java/org/apache/solr/update/TransactionLog.java
new file:
solr/core/src/test-files/solr/configsets/cdcr-cluster1/conf/schema.xml
new file:
solr/core/src/test-files/solr/configsets/cdcr-cluster1/conf/solrconfig.xml
new file:
solr/core/src/test-files/solr/configsets/cdcr-cluster2/conf/schema.xml
new file:
solr/core/src/test-files/solr/configsets/cdcr-cluster2/conf/solrconfig.xml
new file:
solr/core/src/test/org/apache/solr/cloud/CdcrBidirectionalTest.java
{code}
Added testclass CdcrBidirectionalTest where two active clusters are talking to
each other runtime.
The write operations in TransactionLog are repeated in CdcrTransactionLog to
accommodate the extra entry for each update. Repeated code! henceforth planning
to have TLogCommonUtils / UpdateLogCommonUtils to put the common code for both
classes' methods.
Eagerly looking forward to feedback, suggestions and improvements.
> Enabling bi-directional CDCR active-active clusters
> ---------------------------------------------------
>
> Key: SOLR-11003
> URL: https://issues.apache.org/jira/browse/SOLR-11003
> Project: Solr
> Issue Type: Improvement
> Security Level: Public(Default Security Level. Issues are Public)
> Components: CDCR
> Reporter: Amrit Sarkar
>
> 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.
> ClusterACollectionA => ClusterBCollectionB | ClusterBCollectionB =>
> ClusterACollectionA.
> The best use-case would be to we 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.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
