lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SOLR-11003) Enabling bi-directional CDCR on cluster for better failover
Date Mon, 06 Nov 2017 16:14:00 GMT

    [ https://issues.apache.org/jira/browse/SOLR-11003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16240493#comment-16240493
] 

ASF subversion and git services commented on SOLR-11003:
--------------------------------------------------------

Commit a30c92a79cd75d3c4fe21829e70292f8314afd4f in lucene-solr's branch refs/heads/branch_7x
from [~varunthacker]
[ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=a30c92a ]

SOLR-11003: Support bi-directional syncing of cdcr clusters. We still only support actively
into one cluster cluster,
 but have the ability to switch indexing clusters and cdcr will replicate correctly


> 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,
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-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


Mime
View raw message