[
https://issues.jboss.org/browse/ISPN-9003?page=com.atlassian.jira.plugin....
]
William Burns commented on ISPN-9003:
-------------------------------------
Upon further investigation iteration will have to do something different than a simple
get. Otherwise it would cause possible concurrent remove expired operations (up to
numOwners).
There are 2 ways to fix this so far:
1. Use something like a segmented data container ISPN-5451 (prevents all the nodes from
accessing the expired data)
2. We can change the iteration to not remove the entry but rather just report if it should
be used or not. We could even in the case of when it expires set a last access time of a
negative number which is a sign that it shouldn't query remote again (preventing it
from going remote multiple times before entry is removed)
For now #2 will be done and when segment data container is introduced we can move to that
if desired.
Clustered maxIdle expiration
----------------------------
Key: ISPN-9003
URL:
https://issues.jboss.org/browse/ISPN-9003
Project: Infinispan
Issue Type: Enhancement
Reporter: Tristan Tarrant
Assignee: William Burns
Fix For: 9.3.0.Beta1, 9.3.0.Final
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)