[infinispan-issues] [JBoss JIRA] (ISPN-3997) Expired cache entries are not pruned from memory and store on access
Dan Berindei (JIRA)
issues at jboss.org
Fri Feb 14 11:15:30 EST 2014
[ https://issues.jboss.org/browse/ISPN-3997?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12944767#comment-12944767 ]
Dan Berindei commented on ISPN-3997:
------------------------------------
[~mircea.markus], maybe we should create a feature request for this and see if there is demand for it? Size-based eviction can be done on the thread accessing the entry, with {{EvictionThreadPolicy.PIGGYBACK}}, we could do the same for expired entries. That is, unless we go with Sanne's suggestion and eliminate expiration checks in the caller thread completely...
> Expired cache entries are not pruned from memory and store on access
> --------------------------------------------------------------------
>
> Key: ISPN-3997
> URL: https://issues.jboss.org/browse/ISPN-3997
> Project: Infinispan
> Issue Type: Bug
> Components: Eviction
> Affects Versions: 6.0.1.Final, 7.0.0.Alpha1
> Environment: Remote HotRod access to infinispan-server
> Reporter: Wolf-Dieter Fink
> Assignee: Dan Berindei
>
> Due to the documentation expired entries are pruned by having a scheduler or if they are accessed after expiration.
> This will not be done if the key is access.
> In case of having no scheduler to prune the entries this might cause OutOfMemory issues.
--
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
More information about the infinispan-issues
mailing list