[infinispan-dev] Preloading from disk versus state transfer Re: ISPN-1384 - InboundInvocationHandlerImpl should wait for cache to be started? (not just defined)
Galder Zamarreño
galder at redhat.com
Mon Oct 10 06:37:42 EDT 2011
On Oct 4, 2011, at 11:58 PM, Mircea Markus wrote:
>
> On 3 Oct 2011, at 01:09, Manik Surtani wrote:
>
>>
>> On 28 Sep 2011, at 10:56, Dan Berindei wrote:
>>
>>> I'm not sure if the comment is valid though, since the old
>>> StateTransferManager had priority 55 and it also cleared the data
>>> container before applying the state from the coordinator. I'm not sure
>>> how preloading and state transfer are supposed to interact, maybe
>>> Manik can help clear this up?
>>
>> Hmm - this is interesting. I think preloading should happen first, since the cache store may contain old data.
> I can't find Dan's original email - was it set to the entire list?
Yes it was. Dan renamed the subject thread:
http://lists.jboss.org/pipermail/infinispan-dev/2011-September/009128.html
>
> I don't get the entire context, but I don't think preloading *first* would resolve the consistency problem in the case of deletions: what if you preload something that was in between deleted from memory?
> _______________________________________________
> infinispan-dev mailing list
> infinispan-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/infinispan-dev
--
Galder Zamarreño
Sr. Software Engineer
Infinispan, JBoss Cache
More information about the infinispan-dev
mailing list