lucene-solr-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Renaud Delbru <>
Subject Re: CDCR: Help With Tlog Growth Issues
Date Thu, 01 Dec 2016 15:43:18 GMT
Hi Thomas,

Looks like the buffer is enabled on the update log, and even if the 
updates were replicated, they are not removed.

What is the output of the command  `cdcr?action=STATUS` on both cluster ?

If you see in the response `<str name=buffer>enabled</str>`, then the 
buffer is enabled.
To disable it, you should run the command `/cdcr?action=DISABLEBUFFER`.

Kind Regards
Renaud Delbru

On 10/11/2016 23:09, Thomas Tickle wrote:
> I am having an issue with cdcr that I could use some assistance in 
> resolving.
> I followed the instructions found here: 
> The CDCR is setup with a single source to a single target.  Both the 
> source and target cluster are identically setup as 3 machines, each 
> running an external zookeeper and a solr instance.  I’ve enabled the 
> data replication and successfully seen the documents replicated from 
> the source to the target with no errors in the log files.
> However, when examining the /cdcr?action=QUEUES command, I noticed 
> that the tlogTotalSize and tlogTotalCount were alarmingly high.  
> Checking the data directory for each shard, I was able to confirm that 
> there was several thousand logs files of each 3-4 megs.  It added up 
> to almost 35 GBs of tlogs.  Obviously, this amount of tlogs causes a 
> serious issue when trying to restart a solr server after activities 
> such as patch.
> *Is it normal for old tlogs to never get removed in a CDCR setup?*
> **
> Thomas Tickle
> Nothing in this message is intended to constitute an electronic 
> signature unless a specific statement to the contrary is included in 
> this message.
> Confidentiality Note: This message is intended only for the person or 
> entity to which it is addressed. It may contain confidential and/or 
> privileged material. Any review, transmission, dissemination or other 
> use, or taking of any action in reliance upon this message by persons 
> or entities other than the intended recipient is prohibited and may be 
> unlawful. If you received this message in error, please contact the 
> sender and delete it from your computer. 

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message