[infinispan-dev] https://issues.jboss.org/browse/ISPN-977

[Manik Surtani]

On 11 May 2011, at 13:29, Sanne Grinovero wrote:

> First thing I thought when reading your email was "OMG do we support
> on-the-fly hash implementation changes? crazy!"
> 
> That's obviously not the case, but if you name it as
> @ConsistenHashChangeListene that's what I would think.
> 
> Wouldn't it be better to change the exact timing of the viewchange
> event? I don't see why Infinispan users might be more interested in
> knowing about the topology details according to the transport than
> what they are about the actual Infinispan hashing topology - I would
> expect that when I receive which notification the new view is already
> installed and ready to go; actually I thought that was the case since
> ever.
> 
> What would be the use cases to get the notification *before* the new
> hash is installed?

A lot of code makes use of view changes so as to update the consistent hash.  :-)

Also view changes indicate a lower-level change (it is propagated from JGroups) and any service that, for example, relies on a coordinator would need to know if this coordinator changes (such as SingletonCacheStore, etc).
--
Manik Surtani
manik at jboss.org
twitter.com/maniksurtani

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