[
https://issues.apache.org/jira/browse/SOLR-15879?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17465081#comment-17465081
]
Shawn Heisey commented on SOLR-15879:
-------------------------------------
Solr 7.5 is VERY old at this point. It was announced Sep 24, 2018.
This problem is not going to get fixed in 7.x, because 7.x is currently in
maintenance mode. We need to know whether it's still a problem in the latest
8.x version, which is 8.11.1 as I write this. Unless a showstopper problem is
discovered, the next version of Solr that gets released is likely to be 9.0.0.
At that point 7.x will become unsupported and 8.x will move to maintenance
mode. This problem does not qualify as a showstopper, mostly because there is
a workaround – remove maxRamMB and just configure size.
Have you tried LRUCache instead of FastLRUCache to see if it honors the RAM
setting? Note that in 8.x, all cache implementations other than CaffeineCache
are deprecated, most likely to be removed in 9.0.0.
I think the issue title should probably change to "QueryResultCache does not
honor maxRamMB setting" ... a memory leak is a very specific kind of software
bug, and I do not think this is actually a memory leak.
> Memory leak in QueryResultsCache
> --------------------------------
>
> Key: SOLR-15879
> URL: https://issues.apache.org/jira/browse/SOLR-15879
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Components: query
> Affects Versions: 7.5
> Reporter: Harish Kumar Murugesan
> Priority: Major
>
> There is a leak in memory observed when we set _maxRamMB_ parameter in
> QueryResultsCache. In our cache we have set the below configuration:
> _<queryResultCache class="solr.FastLRUCache" size="5000" initialSize="512"
> maxRamMB="1048" autowarmCount="0"/>_
> The number of elements in the cache grown upto 320K in count and the size of
> the cache also went upto 9GB. Only inserts were happening to the cache and no
> evictions observed in the cache. Cache was not getting controlled by both
> size and maxRamMB parameters. If we remove maxRamMB parameter and set only
> the size parameter then the QueryResultsCache is not growing beyond the limit
> set in size parameter. This is observed in SOLR 7.5 version.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org
For additional commands, e-mail: issues-h...@solr.apache.org
