You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Amrit Sarkar (JIRA)" <ji...@apache.org> on 2017/08/28 16:01:00 UTC
[jira] [Comment Edited] (SOLR-11003) Enabling bi-directional CDCR
active-active clusters
[ https://issues.apache.org/jira/browse/SOLR-11003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16143932#comment-16143932 ]
Amrit Sarkar edited comment on SOLR-11003 at 8/28/17 4:00 PM:
--------------------------------------------------------------
[~erickerickson] Are you talking about this? _SOLR-11278: CdcrBootstrapTest failing in branch_6_6_. I am trying to understand what's wrong with it, and have narrowed down to:
All the tests in this class fails where *we stop CDCR, index docs in source and then turns on CDCR again and expect BOOTSTRAP to happen*. If I debug on IDE, all tests passes successfully (as the steps slows down), suggesting the _time to wait for target to sync_ is low. But increasing it to 5 minutes even, instead of default 2 minutes, doesn't work. I increased explicit commit issued while waiting from 1 to 3 second, doesn't work either.
Let me know if there are other tests which are failing too related to CDCR.
was (Author: sarkaramrit2@gmail.com):
[~erickerickson] Are you talking about this? _SOLR-11278: CdcrBootstrapTest failing in branch_6_6_. I am trying to understand what's wrong with it, and have narrowed down to:
All the tests in this class fails where *we stop CDCR, index docs in source and then turns on CDCR again and expect BOOTSTRAP to happen*. If I debug on IDE, all tests passes successfully (as the steps slows down), suggesting the _time to wait for target to sync_ is low. But increasing it to 5 minutes even, instead of default 2 minutes, doesn't work.
Let me know if there are other tests which are failing too related to CDCR.
> 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-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-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org