Hi
We have solr 6.2.1.
One of the collection is causing lots of updates.
We see the next logs:
/INFO org.apache.solr.core.SolrDeletionPolicy :
SolrDeletionPolicy.onCommit: commits: num=2
commit{dir=/opt/solr-6.2.1/server/solr/collection_shard1_replica2/data/index,segFN=segments_qbmv,generation=1228135}
commit{dir=/opt/solr-6.2.1/server/solr/collection_shard1_replica2/data/index,segFN=segments_qbmw,generation=1228136}/
As a result we are running out of memory in the instances hosting the
collection.
The used memory is increased by 1 percent per day.
The used memory is not part of the Solr's JVM, but part of the Slab memory
(which I get to know now :) )
when cat over /proc/meminfo we get:
/
Slab: 17906760 kB
SReclaimable: 17841548 kB
/
and slabtop gives:
91635138 91635138 6% 0.19K 4363578 21 17454312K dentry
~17 GB for dentry.
Is there any way to avoid this "memory leak"?
echo 2 > /proc/sys/vm/drop_caches ; sync is cleaning the this "clean" cache
but -
1. Either from the OS side or from the solr collection side?
2. What's the meaning of the SolrDeletionPolicy logs we get? do we commit
lots of updates? deletes?
Thanks
Gilad
--
View this message in context:
http://lucene.472066.n3.nabble.com/High-increasing-slab-memory-solr-6-tp4309708.html
Sent from the Solr - User mailing list archive at Nabble.com.
