[infinispan-dev] CacheLoaders, Distribution mode and Interceptors

[Dan Berindei]

>

> > Implementation-wise, just changing the interceptor order is probably not
> enough. If the key doesn't exist in the cache, the CacheLoaderInterceptor
> will still try to load it from the cache store after the remote lookup, so
> we'll need a marker  in the invocation context to avoid the extra cache
> store load.
> if the key does't map to the local node it should trigger a remote get to
> owners (or allow the dist interceptor to do just that)
> > Actually, since this is just a performance issue, it could wait until we
> implement tombstones everywhere.
> Hmm, not sure i see the correlation between this and tombstones?
>
>
If the key doesn't exist in the cache at all, on any node, then the remote
lookup will return null and the CacheLoaderInterceptor will try to load it
from the local cache store again (assuming we move CacheLoaderInterceptor
after DistributionInterceptor). If DistributionInterceptor put a tombstone
in the invocation context for that key, CacheLoaderInterceptor could avoid
that extra cache store lookup.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/infinispan-dev/attachments/20130319/e0628f10/attachment.html