[
https://issues.apache.org/jira/browse/SOLR-13003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16694230#comment-16694230
]
Shawn Heisey commented on SOLR-13003:
-------------------------------------
Ouch. The jar is five megabytes!
To use it, you'll need to stop Solr, delete the existing solr-core-7.3.1.jar
file from server/solr-webapp/webapp/WEB-INF/lib and copy this new jar in its
place, then start Solr back up. Before starting Solr again, you will also need
to edit your log4j.properties file to increase the rollover size for the
logfile from 4MB to something much larger. I expect there to be a LOT of data
logged.
Then you'll have to do the steps that result in the cache getting much larger
than the defined size.
> 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: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
