[ https://issues.apache.org/jira/browse/SOLR-11003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16225107#comment-16225107 ]
Varun Thacker commented on SOLR-11003: -------------------------------------- bq. 2 shards instead of 1? The only problem / caveat is the test will become heavier with two separate clusters running already, I hope it don't introduce unnecessary zk-timeouts or such. We'll find out. But I'd be more comfortable testing with 2 shards instead of 1. bq. Also removing CdcrQueue status (it causes no harm though). Sure then let's keep it then. We can add a code comment clarifying that this is only to observe the queue length when the test runs > Enabling bi-directional CDCR on cluster for better failover > ----------------------------------------------------------- > > 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: SOLR-11003-tlogutils.patch, SOLR-11003.patch, > SOLR-11003.patch, SOLR-11003.patch, SOLR-11003.patch, SOLR-11003.patch, > SOLR-11003.patch, SOLR-11003.patch, SOLR-11003.patch, SOLR-11003.patch, > SOLR-11003.patch, sample-configs.zip > > > 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. -- 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