[infinispan-dev] ISPN-1586 - inconsistent cache data in replication cluster with local (not shared) cache store

[Manik Surtani]

Yes, a purgeExceptCoordinator flag makes sense for replicated, but that's it.  For dist it is harder, since to have correct semantics you'd need to iterate through the cache store and purge entries that the current node is not the primary owner for.  That may be a pretty expensive process.

On 14 Dec 2011, at 18:01, Mircea Markus wrote:

> 
> On 14 Dec 2011, at 13:44, Dan Berindei wrote:
> 
>> Hi guys
>> 
>> For a little background, see the discussion at https://issues.jboss.org/browse/ISPN-1586
>> 
>> How do you feel about discarding the contents of the cache store on all cache (virtual) nodes except the first to start?
> I think that's a that might work for replicated caches, but not for distributed. Imagine this scenario: a DIST cluster is turned down for maintenance, now when it is started again the preload data, except the fist node to start, is lost.
>> 
>> Configuring purgeOnStartup="true" is not ok in data grid scenarios, because you'd lose all the data on restart. But loading entries from the cache store of a node that started later is almost guaranteed to lead to stale data. In some use cases that stale data might be acceptable, but in most cases it probably isn't. So perhaps it makes sense to make this configurable?
>> 
>> Cheers
>> Dan
> 
> _______________________________________________
> infinispan-dev mailing list
> infinispan-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/infinispan-dev

--
Manik Surtani
manik at jboss.org
twitter.com/maniksurtani

Lead, Infinispan
http://www.infinispan.org



-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/infinispan-dev/attachments/20111220/713f1b94/attachment-0001.html