Webster Homer commented on SOLR-11724:

This may be a different issue, but I see similar behavior with some replicas in 

We have a number of replicas which have identical schemas. We found that TLOG 
replicas give much more consistent search results.
We created a collection using TLOG replicas in our QA clouds.
We have a locally hosted solrcloud with 2 nodes, all our collections have 2 
shards. We use CDCR to replicate the collections from this environment to 2 
data centers hosted in Google cloud. This seems to work fairly well for our 
collections with NRT replicas. However the new TLOG collection has problems.
The google cloud solrclusters have 4 nodes each (3 separate Zookeepers). 2 
shards per collection with 2 replicas per shard.
We never see data show up in the tlog replica cloud collections, but we do see 
tlog files show up on the cloud servers. I can see that all of the servers have 
cdcr started, buffers are disabled.
The cdcr source configuration is:
The target configurations in the 2 clouds are the same:
"requestHandler":{"/cdcr":{ "name":"/cdcr", "class":"solr.CdcrRequestHandler", 
-rw-r--r-- 1 apache apache 596517718 Feb 28 20:19 
-rw-r--r-- 1 apache apache 647 Feb 28 22:18 
[apache@uc1b-ecomqa-msc01 tlog]$ pwd
All of our collections have a timestamp field, index_date. In the source 
collection all the records have a date of 2/28/2018 but the target collections 
have a latest date of 1/26/2018
I don't see cdcr errors in the logs. 
We have a number of similar collections that behave correctly. This is the only 
collection that is a TLOG collection. It appears that CDCR doesn't support TLOG 
We also see the same behavior in our production solrclouds. The collections 
that use NRT replicas replicate fine with CDCR, the collection that uses TLOG 
replicas do not. Several of the NRT collections have the same configurations as 
the tlog colletion, so that seems to be the only difference between them

> Cdcr Bootstrapping does not cause "index copying" to follower nodes on Target
> -----------------------------------------------------------------------------
>                 Key: SOLR-11724
>                 URL: https://issues.apache.org/jira/browse/SOLR-11724
>             Project: Solr
>          Issue Type: Bug
>      Security Level: Public(Default Security Level. Issues are Public) 
>          Components: CDCR
>    Affects Versions: 7.1
>            Reporter: Amrit Sarkar
>            Priority: Major
>         Attachments: SOLR-11724.patch, SOLR-11724.patch, SOLR-11724.patch, 
> SOLR-11724.patch
> Please find the discussion on:
> http://lucene.472066.n3.nabble.com/Issue-with-CDCR-bootstrapping-in-Solr-7-1-td4365258.html
> If we index significant documents in to Source, stop indexing and then start 
> CDCR; bootstrapping only copies the index to leader node of shards of the 
> collection, and followers never receive the documents / index until and 
> unless atleast one document is inserted again on source; which propels to 
> target and target collection trigger index replication to followers.
> This behavior needs to be addressed in proper manner, either at target 
> collection or while bootstrapping.

This message was sent by Atlassian JIRA

To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org

Reply via email to