[
https://issues.apache.org/jira/browse/SOLR-11003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16096778#comment-16096778
]
Erick Erickson commented on SOLR-11003:
---------------------------------------
I want to be sure I understand the scope here. IIUC, this patch does not allow
simultaneous indexing to both SOURCE and TARGET, correct? I don't consider this
a show-stopper, just making sure I'm looking at it correctly.
If the above is correct, then what happens in this case:
-indexing to collectionA which is using CDCR to forward updates to collectionB
-collectionA goes down for some reason _and_ there are some updates not yet
forwarded to CollectionB
-indexing is switched to collectionB
-collectionA comes back on line as TARGET.
What happens with the updates in collectionA that weren't forwarded? Is
collectionB out of sync in this case? If so how do the collections get back in
sync? If there's an attempt to forward collection A's buffered updates how are
they coordinated with collectionB's updates which may be for the same docs?
I admit I haven't really looked at the code carefully, I'd like an idea of what
the intention is before diving in.
And if my opening question is incorrect and one can index to both collections
simultaneously, how does it work when the same document is sent go both
collectionA and collectionB independently?
> 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-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-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
