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
Thanks Erick - that's what we have settled on doing until we are using
SolrCloud, which will be later this year with any luck. We want to get up
onto Solr 5.5.1 first (ASAP) and we tried disabling tlogs today and that
seems to fit the bill.
If you are NOT using SolrCloud and don't
care about Real Time Get, you can just disable the
tlogs entirely. They're not doing you all that much
good in that case...
The tlogs are irrelevant when it comes to master/slave
replication.
FWIW,
Erick
On Fri, Jun 17, 2016 at 9:14 AM, Chris Morley
After some more searching, I found a thread online where Erick Erickson is
telling someone about how there are old tlogs left around in case there is
a need for a peer to sync even if SolrCloud is not enabled. That makes
sense, but we'll probably want to enable autoCommit and then trigger
