[infinispan-dev] Preloading from disk versus state transfer Re: ISPN-1384 - InboundInvocationHandlerImpl should wait for cache to be started? (not just defined)

[Sanne Grinovero]

>>
>> Can't you just skip loading state and be happy with the state you
>> receive from peers? More data will be lazily loaded.
>> Applying of course only when you're not the only/first node in the
>> grid, in which case you have to load.
>>
>
> Right, we could preload only on the first node. With a shared cache
> store this should work great, we just have to start preloading after
> we connect to the cluster and before we send the join request.
>
> But I have trouble visualizing how a persistent (purgeOnStartup =
> false) non-shared cache store should to work until we have some
> validation mechanism like in
> https://issues.jboss.org/browse/ISPN-1195. Should we even allow this
> kind of setup?

Right I don't think it makes much sense. The current node might have
been down for a long time and it's dedicated cacheloader will likely
contain stale values; we might update older values via versions of
optimistic locking, but we won't be able to remove those which should
have been removed.
I don't think we should support that, at least until these problems are solved.