[
https://issues.apache.org/jira/browse/SOLR-13003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16694354#comment-16694354
]
Shalin Shekhar Mangar commented on SOLR-13003:
----------------------------------------------
The default queryResultCache implementation is the LRUCache which supports
maxRamMB and that is tested. You are using the FastLRUCache for query result
cache. This combination is not tested. I think that's where the problem lies.
Do you mind switching query result cache back to LRUCache. Was there are a
reason you made the switch?
I'll look into how query result cache using FastLRUCache triggers this bug and
either fix it or disable the specific combination.
> Query Result Cache does not honour maxRamBytes parameter
> --------------------------------------------------------
>
> Key: SOLR-13003
> URL: https://issues.apache.org/jira/browse/SOLR-13003
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Affects Versions: 7.3.1
> Reporter: Cetra Free
> Priority: Major
> Attachments: CLRU-logging.patch, lrucacheexpanded.png,
> lrucachemaxmb.png, solr-core-7.3.1-SNAPSHOT.jar, solrconfig.xml
>
>
> When using the maxRamBytes parameter with the queryResultCache directive, we
> have seen the retained size of the cache orders of magnitude larger than what
> is configured.
> Please see attached VisualVM output which shows the retained size is about
> 1.5gb, but the maxRamBytes is set to 64mb.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
