lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Amrit Sarkar (JIRA)" <>
Subject [jira] [Commented] (SOLR-11003) Enabling bi-directional CDCR active-active clusters
Date Mon, 28 Aug 2017 11:25:02 GMT


Amrit Sarkar commented on SOLR-11003:

The patch is failing on {{master}} and previous versions:  {{branch_6_5}}

[junit4]   2> Caused by: java.util.concurrent.ExecutionException: org.apache.solr.client.solrj.impl.HttpSolrClient$RemoteSolrException:
Error from server at Invalid shift
value (64) in prefixCoded bytes (is encoded value really an INT?)
   [junit4]   2> 	at
   [junit4]   2> 	at java.util.concurrent.FutureTask.get(
   [junit4]   2> 	at org.apache.solr.handler.CdcrRequestHandler.handleCollectionCheckpointAction(
   [junit4]   2> 	... 34 more 

bq. Invalid shift value (64) in prefixCoded bytes (is encoded value really an INT?)

Need to fix this for {{CollectionCheckpoint}}.

> Enabling bi-directional CDCR active-active clusters
> ---------------------------------------------------
>                 Key: SOLR-11003
>                 URL:
>             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.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.
> 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

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message