[ 
https://issues.apache.org/jira/browse/SOLR-5080?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13721993#comment-13721993
 ] 

Kranti Parisa commented on SOLR-5080:
-------------------------------------

Sure, new searcher will invalidate the caches. But the use cases are we don't 
want to expire the other caches than FilterCache. And for us the filters are 
time bounded, for every 5 minutes the availability changes. I am trying to set 
up a multi core environment and use joins (with FQ). Replication happens for 
every 30 min. If we open a new searcher for every 5 min, then all the other 
caches are also invalidated and during runtime it may cost us to rebuild those 
caches. Instead of that, the idea is to have a facility to configure the 
FilterCaches with 5 min expiration policy on one of the cores (where 
availability changes every 5 min) so that we can maintain the JVM sizes which 
will also be an imp factor on high load.

So, you suggest to open new searcher which will invalid all the caches on the 
specific core?
                
> Ability to Configure Expirable Caches (use Google Collections - 
> MapMaker/CacheBuilder for SolrCache)
> ----------------------------------------------------------------------------------------------------
>
>                 Key: SOLR-5080
>                 URL: https://issues.apache.org/jira/browse/SOLR-5080
>             Project: Solr
>          Issue Type: New Feature
>            Reporter: Kranti Parisa
>
> We should be able to configure the expirable caches, especially for 
> filterCaches. In some cases, the filterCaches are not valid beyond certain 
> time (example 5 minutes). 
> Google collections has MapMaker/CacheBuilder which does allow expiration
> http://google-collections.googlecode.com/svn/trunk/javadoc/com/google/common/collect/MapMaker.html
> http://docs.guava-libraries.googlecode.com/git/javadoc/com/google/common/cache/CacheBuilder.html
> SolrCache, LRUCache etc can be implemented with MapMaker or CacheBuilder

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

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

Reply via email to