lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Amrit Sarkar (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (SOLR-11003) Enabling bi-directional CDCR active-active clusters
Date Tue, 04 Jul 2017 11:43:00 GMT

     [ https://issues.apache.org/jira/browse/SOLR-11003?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Amrit Sarkar updated SOLR-11003:
--------------------------------
    Description: 
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 forwarded the
updates to ClusterBCollectionB. If ClusterACollectionA gets down, we point the indexer and
searcher application to ClusterBCollectionB. Once ClusterACollectionA is up, depending updates
count, they will be bootstrapped or forwarded to ClusterACollectionA from ClusterBCollectionB.

  was:
The latest version of Solr CDCR across clusters is in active-passive format, where we can
index into source cluster 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 clusters and the updates gets reflected
across the clusters in real-time. ClusterA => ClusterB | ClusterB => ClusterA.

The best use-case would be to we keep indexing in ClusterA which forwarded the updates to
ClusterB. If ClusterA gets down, we point the indexer and searcher application to ClusterB.
Once ClusterA is up, depending updates count, they will be bootstrapped or forwarded to ClusterA
from ClusterB.


> 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
>
> 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 forwarded
the updates to ClusterBCollectionB. If ClusterACollectionA gets down, we point the indexer
and searcher application to ClusterBCollectionB. Once ClusterACollectionA is up, depending
updates count, they will be bootstrapped or forwarded to ClusterACollectionA from 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