Hi Shamik, I agree that your filter cache is not the reason for OOMs. Can you confirm that your fieldCache and filedValueCache sizes are not consuming too much memory. The next on the list would be some heavy faceting with pivots, but you mentioned that all fields are low cardinality. Do you see any extremely slow queries in your logs? Can you check if there are some deep paging queries? If nothing else, you can always do heap dump and see what’s in it.
And about your filterCache hit ratio: how frequently do you commit? With 400 rq/h it can be that filters are not repeated between two commits. Do you have high eviction rate? Thanks, Emir -- Monitoring - Log Management - Alerting - Anomaly Detection Solr & Elasticsearch Consulting Support Training - http://sematext.com/ > On 20 Oct 2017, at 20:10, shamik <sham...@gmail.com> wrote: > > Zisis, thanks for chiming in. This is really an interesting information and > probably in line what I'm trying to fix. In my case, the facet fields are > certainly not high cardinal ones. Most of them have a finite set of data, > the max being 200 (though it has a low usage percentage). Earlier I had > facet.limit=-1, but then scaled down to 200 to eliminate any performance > overhead. > > I was not aware of maxRamMB parameter, looks like it's only available for > queryResultCache. Is that what you are referring to? Can you please share > your cache configuration? > > > > -- > Sent from: http://lucene.472066.n3.nabble.com/Solr-User-f472068.html
