From what is see it basically duplicates the index files, but does not delete the old ones. It uses caffeine cache.
What I observe is that there is an exception when shutting down for the collection that is updated - timeout waiting for all directory ref counts to be released - gave up waiting on CacheDir. > Am 20.01.2020 um 11:26 schrieb Jörn Franke <jornfra...@gmail.com>: > > Sorry I missed a line - not tlog is growing but the /data/index folder is > growing - until restart when it seems to be purged. > >> Am 20.01.2020 um 10:47 schrieb Jörn Franke <jornfra...@gmail.com>: >> >> Hi, >> >> I have a test system here with Solr 8.4 (but this is also reproducible in >> older Solr versions), which has an index which is growing and growing - >> until the SolrCloud instance is restarted - then it is reduced tot the >> expected normal size. >> The collection is configured to do auto commit after 15000 ms. I expect the >> index grows comes due to the usage of atomic updates, but I would expect >> that due to the auto commit this does not grow all the time. >> After the atomic updates a commit is done in any case. >> >> I don’t see any error message in the log files, but the growth is quiet >> significant and frequent restarts are not a solution of course. >> >> Maybe I am overlooking here a tiny configuration issue? >> >> Thank you. >> >> >> Best regards
