[infinispan-dev] Asymmetric caches and manual rehashing design

[Mircea Markus]

Nice stuff.

Some q:

- When a node CM that has c1 and c2 caches running on it goes down, you'll end up having  REQUEST_LEAVE(c1) and REQUEST_LEAVE(c2) at the same time. Is this handled in serial or in parallel?

- The view updates can be disabled dynamically (DISABLE_VIEW_UPDATES). Shouldn't we also be able to re-enabled them manually after that?

The view accept handler updates the pending view acquires the view change lock in exclusive mode, then releases it immediately
Shouldn't this be:
- acquire exclusive lock
- updates the pending view
- release lock
?

On 27 Sep 2011, at 17:22, Dan Berindei wrote:

> Following the discussions last week I've written up a wiki page
> describing the strategies for cache view management and state transfer
> that will enable asymmetric caches and manual rehashing:
> http://community.jboss.org/wiki/AsymmetricCachesAndManualRehashingDesign
> 
> The state transfer part is not very detailed, as you'll see we want to
> go with a non-blocking approach but I'm not sure we can finish that
> for 5.1 so we're keeping a blocking fallback option.
> 
> Your comments are welcome, either on the list or on the wiki page.
> 
> Dan
> _______________________________________________
> infinispan-dev mailing list
> infinispan-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/infinispan-dev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/infinispan-dev/attachments/20110928/2dfadb87/attachment.html