[
https://issues.apache.org/jira/browse/SOLR-14202?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17026261#comment-17026261
]
Jörn Franke commented on SOLR-14202:
------------------------------------
I did some further investigation. In fact, during the commit a new searcher is
opened. However, after each load an additional searcher is opened.
After the first load i have one searcher, after the second load 2, after the
third load 3 etc. The strange thing is that the registered time for them is
always the same. So after load 3 I have 3 searcher all registeed at exactly the
same time (to the ms). Is this normal?
Could it be that my zookeeper is corrupted (not Zookeeper itself, but may due
to some of the upgrades)?
> Old segments are not deleted after commit
> -----------------------------------------
>
> Key: SOLR-14202
> URL: https://issues.apache.org/jira/browse/SOLR-14202
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Components: SolrCloud
> Affects Versions: 8.4
> Reporter: Jörn Franke
> Priority: Major
> Attachments: eoe.zip
>
>
> The data directory of a collection is growing and growing. It seems that old
> segments are not deleted. They are only deleting during start of Solr.
> How to reproduce. Have any collection (e.g. the example collection) and start
> indexing documents. Even during the indexing the data directory is growing
> significantly - much more than expected (several magnitudes). if certain
> documents are updated (without significantly increasing the amount of data)
> the index data directory grows again several magnitudes. Even for small
> collections the needed space explodes.
> This reduces significantly if Solr is stopped and then started. During
> startup (not shutdown) Solr purges all those segments if not needed (*
> sometimes some but not a significant amount is deleted during shutdown). This
> is of course not a good workaround for normal operations.
> It does not seem to have a affect on queries (their performance do not seem
> to change).
> The configs have not changed before the upgrade and after (e.g. from Solr 8.2
> to 8.3 to 8.4, not cross major versions), so I assume it could be related to
> Solr 8.4. It may have been also in Solr 8.3 (not sure), but not in 8.2.
>
> IndexConfig is pretty much default: Lock type: native, autoCommit: 15000,
> openSearcher=false, autoSoftCommit -1 (reproducible with autoCommit 5000).
> Nevertheless, it did not happen in previous versions of Solr and the config
> did not change.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org
