Re: Weird transaction log behavior with CDCR

2018-04-17 Thread Amrit Sarkar
Chris, Try to index few dummy documents and analyse if the tlogs are getting cleared or not. Ideally on the restart, it clears everything and keeps max 2 tlog per data folder. Amrit Sarkar Search Engineer Lucidworks, Inc. 415-589-9269 www.lucidworks.com Twitter http://twitter.com/lucidworks Linke

Re: Weird transaction log behavior with CDCR

2018-04-17 Thread Chris Troullis
Hi Amrit, thanks for the reply. I shut down all of the nodes on the source cluster after the buffer was disabled, and there was no change to the tlogs. On Tue, Apr 17, 2018 at 12:20 PM, Amrit Sarkar wrote: > Chris, > > After disabling the buffer on source, kind shut down all the nodes of > sour

Re: Weird transaction log behavior with CDCR

2018-04-17 Thread Amrit Sarkar
Chris, After disabling the buffer on source, kind shut down all the nodes of source cluster first and then start them again. The tlogs will be removed accordingly. BTW CDCR doesn't abide by 100 numRecordsToKeep or 10 numTlogs. Amrit Sarkar Search Engineer Lucidworks, Inc. 415-589-9269 www.lucidwo

Re: Weird transaction log behavior with CDCR

2018-04-17 Thread Susheel Kumar
DISABLEBUFFER on source cluster would solve this problem. On Tue, Apr 17, 2018 at 9:29 AM, Chris Troullis wrote: > Hi, > > We are attempting to use CDCR with solr 7.2.1 and are experiencing odd > behavior with transaction logs. My understanding is that by default, solr > will keep a maximum of 1

Weird transaction log behavior with CDCR

2018-04-17 Thread Chris Troullis
Hi, We are attempting to use CDCR with solr 7.2.1 and are experiencing odd behavior with transaction logs. My understanding is that by default, solr will keep a maximum of 10 tlog files or 100 records in the tlogs. I assume that with CDCR, the records will not be removed from the tlogs until it ha