anonymous wrote :
| This depends on which eviction policy you use. If you use the expiration policy, the
expiry time is encoded as data on a node which means it will replicate to B and get
evicted at the appropriate time.
|
Thats good to know, i know you can set a max number of nodes on this but can you set a
minimum? I have the scenario where if it goes past a certain time i.e its stale then ask
data source for data however if data source is not available then use stale data. So does
the expiration policy keep a minimum amount of stale data or will it purge all data that
has gone past the expiration time?
Now to get back to the main point, why it doesnt make sense to run CCL in LOCALMODE. Just
referring back to the example given and the comment
anonymous wrote :
| Now if the cluster is not replicated, nodes A, B and C would have different state,
potentially using the same Fqns. And using a CCL here could result in meaningless state
retrieval.
|
That really a case if you cared about the state of data between the nodes. For my
application, what defines whether to use the value, is the time duration. So I dont care
what the value/state is as long as its not older than X mins old. If is older than Xmins
old then a new value is retrieved.
I do see that it breaks the concept of what a cache loader is if you were allowed to use
CCL in LOCAL mode but i do think there is a need to have something like CCL in local mode.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4148610#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...