On 7/3/2019 1:36 AM, Avi Steiner wrote:
We had some cases with customers (Solr 5.3.1, one search node, one shard) with
huge tlog files (more than 1 GB).
With 30 seconds on the autoCommit, that should not be happening.
When a hard commit fires, the current tlog is closed and a new one
starts.
gt; 4. We can't upgrade to version greater than 7.3.1 currently. The question is
> there something in commit/tlog management that was improved in 7.3.1?
>
> Thanks again.
>
>
> -Original Message-
> From: Erick Erickson
> Sent: Wednesday, July 3, 2019 6
as improved in 7.3.1?
Thanks again.
-Original Message-
From: Erick Erickson
Sent: Wednesday, July 3, 2019 6:42 PM
To: solr-user@lucene.apache.org
Subject: Re: tlog/commit questions
External Email: Don’t open links/attachments from untrusted senders
Let’s take this a piece at a time.
Let’s take this a piece at a time.
1. commit failures are very rare, in fact the only time I’ve seen them is when
running out of disk space, OOMs, pulling the plug, etc. Look in your log files,
is there any evidence of same?
2. OOM messages. To support Real Time Get, internal structures are ke
Hi
We had some cases with customers (Solr 5.3.1, one search node, one shard) with
huge tlog files (more than 1 GB).
Our settings:
1
3
false
