Re: Solr 7.2.0 CDCR Issue with TLOG collections

Webster, I updated the JIRA: *SOLR-12057 , **CdcrUpdateProcessor* has a hack, it enable *PEER_SYNC* to bypass the leader logic in *DistributedUpdateProcessor.versionAdd,* which eventually ends up in segments not getting created. I wrote a very

Re: Solr 7.2.0 CDCR Issue with TLOG collections

seems that this is a bug in Solr https://issues.apache.org/jira/browse/SOLR-12057 Hopefully it can be addressed soon! On Mon, Mar 5, 2018 at 4:14 PM, Webster Homer wrote: > I noticed that the cdcr action=queues returns different results for the > target clouds. One

Re: Solr 7.2.0 CDCR Issue with TLOG collections

I noticed that the cdcr action=queues returns different results for the target clouds. One target says that the updateLogSynchronizer is stopped the other says started. Why? What does that mean. We don't explicitly set that anywhere {"responseHeader": {"status": 0,"QTime": 0},"queues":

Re: Solr 7.2.0 CDCR Issue with TLOG collections

It looks like the data is getting to the target servers. I see tlog files with the right timestamps. Looking at the timestamps on the documents in the collection none of the data appears to have been loaded. In the solr.log I see lots of /cdcr messages action=LASTPROCESSEDVERSION,