reload after eviction in a clustered config

[visionlink]

i understand that after a node has been evicted from the cache, the next time it is requested, the caller will simply get a null. in a clustered config, is there any way to configure TreeCache so that it would attempt to load the value from a neighbor before returning null? if not, what would be the effort to add such functionality (i'd be *more* than willing to work on such code).

thanks.

[ben.wang]

The CacheLoader in 1.1 release can persist the evicted data. So you can retrieve from the backend store the next time.

-Ben

[visionlink]

"bwang00" wrote:
The CacheLoader in 1.1 release can persist the evicted data. So you can retrieve from the backend store the next time.

when the CacheLoader reads the transient data from the data store, does it do a "put" on the cache? that is, does it replicate the data to the rest of the nodes in the cluster? if so, that's not really what i'm looking for. i'd like to allow the nodes in the cluster to show signs of data locality.

-l

[belaban]

No, it doesn't replicate: we use _put() (the internal put()).
You can also write your own CacheLoader impl, which could delegate to another Cache, resulting in a cache hierarchy

Bela