[ https://issues.apache.org/jira/browse/SOLR-11003?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Amrit Sarkar updated SOLR-11003: -------------------------------- Attachment: SOLR-11003.patch The problem was with the refracting of the code where the common portions of TLog and CdcrTLog takien into Utils class. I reverted back to old code now, w/o utils, will figure out how to refractor. Yes, there is repetitive code but I think that's necessary considering we are about to put an extra entry for cdcr updates. {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} Beasts of 100 rounds are passed successfuly. > 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 > Assignee: Varun Thacker > Attachments: sample-configs.zip, SOLR-11003.patch, SOLR-11003.patch, > SOLR-11003.patch, SOLR-11003.patch, SOLR-11003.patch, SOLR-11003.patch, > SOLR-11003-tlogutils.patch > > > 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