[
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
PF the latest, it is the same as the last. These two lines changed:
bq. CollectionAdminRequest.createCollection("cdcr-cluster1",
"cdcr-cluster1", 2, 1)
.withProperty("solr.directoryFactory",
"solr.StandardDirectoryFactory")
.setMaxShardsPerNode(2)
.process(cluster1.getSolrClient());
bq. CollectionAdminRequest.createCollection("cdcr-cluster2",
"cdcr-cluster2", 2, 1)
.withProperty("solr.directoryFactory",
"solr.StandardDirectoryFactory")
.setMaxShardsPerNode(2)
.process(cluster2.getSolrClient());
bq. long maxVersion_c1 =
Math.min((long)CdcrTestsUtil.getFingerPrintMaxVersion(cluster1SolrClient,
"shard1", numDocs),
(long)CdcrTestsUtil.getFingerPrintMaxVersion(cluster1SolrClient,
"shard2", numDocs));
long maxVersion_c2 =
Math.min((long)CdcrTestsUtil.getFingerPrintMaxVersion(cluster2SolrClient,
"shard1", numDocs),
(long)CdcrTestsUtil.getFingerPrintMaxVersion(cluster2SolrClient,
"shard2", numDocs));
> 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, 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: [email protected]
For additional commands, e-mail: [email protected]
