[ 
https://issues.apache.org/jira/browse/SOLR-10478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Cassandra Targett resolved SOLR-10478.
--------------------------------------
    Resolution: Won't Fix

This issue has been open for potential documentation improvements, but none 
have been suggested. The Ref Guide now is pretty clear on precedence with these 
params:

{noformat}
When both size and maxRamMB limits are specified the behavior will differ among 
implementations: in CaffeineCache the maxRamMB limit will take precedence and 
the size limit will be ignored, while in LRUCache and FastLRUCache both limits 
will be observed, with entries being evicted whenever any of the limits is 
reached.
{noformat}

> cache 'size' is ignored if 'maxRamMB' is set -- confusing
> ---------------------------------------------------------
>
>                 Key: SOLR-10478
>                 URL: https://issues.apache.org/jira/browse/SOLR-10478
>             Project: Solr
>          Issue Type: Improvement
>            Reporter: David Smiley
>            Priority: Minor
>
> I thought perhaps I could set both {{size}} and {{maxRamMB}} and Solr would 
> use both.  Nope; apparently {{maxRamMB}} has precedence.  Solr should log a 
> warning or even throw an error if the user does this.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to