Re: default values for numRecordsToKeep and maxNumLogsToKeep

2017-07-20 Thread Erick Erickson
bq: I am pretty sure that anytime a core starts for *any* reason, all the transaction logs that are present will get replayed. This isn't quite true. If Solr is shut down gracefully, or a hard commit happened before shutdown (with no new docs added) then the tlog will _not_ be replayed on startup

Re: default values for numRecordsToKeep and maxNumLogsToKeep

2017-07-20 Thread Shawn Heisey
On 7/18/2017 11:53 AM, suresh pendap wrote: > After looking at the source code I see that the default values for > numRecordsToKeep is 100 and maxNumLogsToKeep is 10. > > So it seems by default the replica can only have 1000 document updates lag > before the replica goes for a Full recovery from th

Re: default values for numRecordsToKeep and maxNumLogsToKeep

2017-07-18 Thread Erick Erickson
I'm going to punt on the rationale since I wasn't involved in that discussion. numRecordsToKeep can be configured in the section of solrconfig.xml if you want to change it though. Best, Erick On Tue, Jul 18, 2017 at 10:53 AM, suresh pendap wrote: > Hi, > After looking at the source code I see

default values for numRecordsToKeep and maxNumLogsToKeep

2017-07-18 Thread suresh pendap
Hi, After looking at the source code I see that the default values for numRecordsToKeep is 100 and maxNumLogsToKeep is 10. So it seems by default the replica can only have 1000 document updates lag before the replica goes for a Full recovery from the leader. I would like to know the rationale for