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

2011-12-14 Thread Dan Berindei
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?

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@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/infinispan-dev

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

2011-12-14 Thread Mircea Markus

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@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/infinispan-dev