Hi, I use solr for distributed indexing in cloud mode. I run solr in kubernetes on a 72 core, 256 GB sever. In the work im doing, i benchmark index times so we are constantly indexing, and then deleting the collection, etc for accurate benchmarking on certain size of GB. In theory, this should not cause a memory build up but it does. As we index more and more (create collections) and then delete the collections, we are still seeing a build up in percentages from kubernetes metric tracking of our server. We are running Solr 7.6 and ZK 3.5.5. Is there any reason why collections are being "deleted" but data stays persistent on the shards that do not release memory, therefore causing a build up and then solr shards will crash for OOM reasons even if they have no collections or "data" on them after we delete each time.
Let me know if anyone has seen this. Thanks Kevin
