Hmmm. Probably won't quite work for us - we need the timeToLiveSeconds behavior in
LRU policy. To mimic that, we'd need to set a new ExpirationPolicy time on every get,
which would kill performance (due to replication).
One thing that I'm thinking is adding a ClusteredCacheLoader. So if one server evicts
too soon (due to node having been read on a different server recently), the
ClusteredCacheLoader will get it from the other cache. When a node is evicted on all
servers in the cluster, then it's when we really wanted to evict.
Does that sound like it might work? Question about ClusteredCacheLoader, since I've
never used it. If we've got 4 servers in the cluster, and a node has been evicted
from 3 of them, are we okay? Does the ClusteredCacheLoader search all other servers in
the cluster until it finds the node?
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4148397#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...