[infinispan-issues] [JBoss JIRA] (ISPN-3997) Expired cache entries are not pruned from memory and store on access
[
https://issues.jboss.org/browse/ISPN-3997?page=com.atlassian.jira.plugin....
]
Mircea Markus commented on ISPN-3997:
-------------------------------------
Indeed the entries from memory (or persistent store for that matter) are not purged, if
expired, during access. What actually happens is that we do check in callers thread to
make sure that the entry is expired or not before returning it to the user[1].
The documentation should rather read: "if the user gets an entry that has been
expired but not purged by the eviction thread yet, then null will be returned to the user.
Note that this doesn't remove the entry from the grid yet, but this would happen when
the eviction thread kicks in"
[1] e.g. in the
[JdbcStringBasedCacheStore|https://github.com/mmarkus/infinispan/blob/mast...
]
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