[infinispan-dev] configuring fetchInMemoryState for topology caches

[Dan Berindei]

On Tue, Jul 9, 2013 at 12:48 PM, Mircea Markus <mmarkus at redhat.com> wrote:

>
> On 21 May 2013, at 17:09, Dan Berindei <dan.berindei at gmail.com> wrote:
>
> > I wouldn't want to deprecate CCL, I think it definitely has a purpose -
> at least in invalidation mode.
> The only use case I'm aware of for invalidation is 2nd level cache and I
> don't think that needs a remote cache, Galder wdyt?
>

I don't know if 2nd level cache actually uses ClusterCacheLoader, but it
could definitely use it without exposing the cache through HotRod.

>
> > Even in replication mode, having a lazy alternative to state transfer
> may be useful. Maybe not for the topology cache, but it might make sense
> for large caches.
>
> this makes me wonder: what would be the case in which one doesn't want to
> use state transfer for a distributed/replicated cache.
>

In replication mode, if the cache has a huge (non-shared) cache store, some
users may prefer to disable fetchPersistentState and rely on
ClusterCacheLoader instead for less frequently accessed keys.

I don't know if it ever makes sense to use ClusterCacheLoader in
distribution mode, since it always sends the ClusteredGetCommand to the
entire cluster.


Cheers
Dan
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/infinispan-dev/attachments/20130710/5eae96c8/attachment.html