lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Varun Thacker (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (SOLR-11003) Enabling bi-directional CDCR on cluster for better failover
Date Sat, 28 Oct 2017 18:22:00 GMT

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

Varun Thacker updated SOLR-11003:
---------------------------------
    Attachment: SOLR-11003.patch

Hi Amrit,

Patch looks very close! 

Uploaded new patch. Removed some sleep waits, changed System.out.println to use a  logger,

 removed unused imports added CHANGES etc.

I think we still need to work on the tests a little more . Here are my two concerns 

1. What are we trying to test with this part?

{code}
      response = CdcrTestsUtil.getCdcrQueue(cluster1SolrClient);
      log.info("Cdcr cluster1 queue response: " + response.getResponse());
      response = CdcrTestsUtil.getCdcrQueue(cluster2SolrClient);
      log.info("Cdcr cluster2 queue response: " + response.getResponse());
{code}

2. We should change the collections to be 2 shards instead of 1. It's probably have better
test coverage for DBQs etc.

You would need to check the individual shards for the fingerprint and checkpoint matches so
it might require some additional work.

> 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, 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