[
https://issues.jboss.org/browse/ISPN-694?page=com.atlassian.jira.plugin.s...
]
Mircea Markus commented on ISPN-694:
------------------------------------
Here's a concern I have for entries written with maxIdle. owners(k) = {N1, N2}
- if entry is read on N1 repeatedly, and never on N2. then N2 will deceide that maxIdle
time has passed and remove the entry
- this will never happen on N1, as max might never be reached
Also a notification will only be triggered on N2, and not on N1.
I guess people using maxIdle don't have high consistency guarantees, but this behavior
is pretty awkward and should be documented accordingly.
I would also be curious to hear [~william.burns] thoughts on whether this functionality
can be exposed over clustered listeners (and then remote listeners).
Create expiration notification for in-memory cache entries
----------------------------------------------------------
Key: ISPN-694
URL:
https://issues.jboss.org/browse/ISPN-694
Project: Infinispan
Issue Type: Feature Request
Components: Eviction
Environment: any
Reporter: Edouard Boily
Assignee: Galder ZamarreƱo
Attachments: 01.patch
Create a CacheEntryExpired notification and make EvictionManager send this notification
when a cache entry is evicted because it is expired.
Also mage sure the cache entry value is sent over in the event.
CacheEntryEvicted notification should also send the entry value in the event.
--
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