Hi Guys
We have faced an issue where tlog size is increasing unnecessarily. We are
using a "heavy indexing, heavy query" approach. We enabled hard commit
also,
solr cloud: 6.6
zk: 3.4.10
shards: 2, replication factor= 2
solrconfig,
<autoCommit>
<maxTime>${solr.autoCommit.maxTime:15000}</maxTime>
<maxDocs>10000</maxDocs>
<openSearcher>false</openSearcher>
</autoCommit>
<!-- softAutoCommit is like autoCommit except it causes a
'soft' commit which only ensures that changes are visible
but does not ensure that data is synced to disk. This is
faster and more near-realtime friendly than a hard commit.
-->
<autoSoftCommit>
<maxTime>${solr.autoSoftCommit.maxTime:15000}</maxTime> -->
</autoSoftCommit>
In every replica, tlog is increasing for more than 200GB which exhaust disk
space. Please suggest someting
On Fri, 19 Mar 2021 at 16:36, Ritvik Sharma <[email protected]> wrote:
> Hi Guys
>
> We have faced an issue where tlog size is increasing unnecessarily. We are
> using a "heavy indexing, heavy query" approach. We enabled hard commit
> also,
>
> solr cloud: 6.6
> zk: 3.4.10
> shards: 2, replication factor= 2
>
>
> solrconfig,
>
> <autoCommit>
> <maxTime>${solr.autoCommit.maxTime:15000}</maxTime>
> <maxDocs>10000</maxDocs>
> <openSearcher>false</openSearcher>
>
>
> </autoCommit>
>
> <!-- softAutoCommit is like autoCommit except it causes a
> 'soft' commit which only ensures that changes are visible
> but does not ensure that data is synced to disk. This is
> faster and more near-realtime friendly than a hard commit.
> -->
>
> <autoSoftCommit>
> <maxTime>${solr.autoSoftCommit.maxTime:15000}</maxTime> -->
> </autoSoftCommit>
>
>
