[ https://issues.jboss.org/browse/ISPN-9003?page=com.atlassian.jira.plugin.... ] William Burns commented on ISPN-9003: ------------------------------------- We already have a timer task, the expiration reaper :) Also state transfer entities are not refreshed from an iterator invocation (they only refresh on a get or write operation). In regards to divergent clocks, this is not an issue as long as we don't send timestampes across nodes (which we don't). Every node uses the provided offset of its own current time to detect expiration. Thus since writes should occur somewhat close to each other in absolute time the expiration of various nodes would be done with only a time differential of just about the latency time between primary and backup. So this could cause an entry to be resurrected if someone read it between this time, but tbh this seems more than okay to me. Lifespan works in a similar fashion, but it actually errs on the other side in that if it expired on any node it assumes all are expired (which is much less costly network wise). -- This message was sent by Atlassian JIRA (v7.5.0#75005)