On 6/16/2016 1:18 PM, Chris Morley wrote: > In Solr 4.10.3 tlogs ARE deleted after issuing update?commit=true. > (And deleted immediately.)
That seems like a bug to me. A hard commit is supposed to close the current transaction log and prune old logs such that what's left will meet the "keep" requirements. It is not designed to delete ALL of the transaction logs. > In Solr 5.5.1 tlogs ARE NOT deleted after issuing update?commit=true. As I understand it, the default "keep requirements" are 10 logs or 100 documents. My guess would be that this means that if each transaction log only contains 1 document, Solr would keep 100 of them ... but if the newest transaction log (the one just closed) contains a million documents, it might only keep the newest one. The hard commit will trim the oldest logs to meet these requirements. This means that if you index a gigabyte or more of data without any commits, and then do a hard commit, Solr will keep at LEAST that latest and largest logfile around, because it's the only way it can guarantee a replay of at least 100 documents. The large log will stick around until additional logfiles are created that meet the requirement. Thanks, Shawn
