[infinispan-dev] Asymmetric caches and manual rehashing design

[Bela Ban]

My 5 cents:

Virtual Cache Views:
================


- The REQUEST_VIEW_UPDATE is a good idea to manually trigger flushing of 
pending views. However, I'm not sure what the goal of 
DISABLE_VIEW_UPDATES is. Since I assume this is for the entire cluster, 
can 1 member disable view delivery for the entire cluster ? What 
scenario is this for ?

- Are you clubbing (virtual) view updates and rebalancing together ? And 
if so (I should probably read on first...), can't you have view 
installations *without* rebalancing ?

- Do we need the complex PREPARE_VIEW / ROLLBACK_VIEW / COMMIT_VIEW 2PC 
handling ? This adds a lot of complexity. Is it only used when we have a 
transactional cache ?

- State is to be transferred *within* this 2PC time frame. Hmm, again, 
this ties rebalancing and view installation together (see my argument 
above)...





On 9/27/11 6:22 PM, 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.


-- 
Bela Ban
Lead JGroups (http://www.jgroups.org)
JBoss / Red Hat