Re: [infinispan-dev] Keeping track of locked nodes
Well, a view change may not mean that the nodes prepared on have changed. But still,
there would almost certainly be a better way to do this than a collection of addresses.
So the goal is to determine whether the set of nodes the prepare has been sent to and the
current set of affected nodes at the time of commit has changed? And what are the
consequences of getting this (pessimistically) wrong, just that the prepare gets repeated
on some nodes?
On 20 Jan 2012, at 03:54, Mircea Markus wrote:
On 19 Jan 2012, at 19:22, Sanne Grinovero wrote:
> I just noticed that org.infinispan.transaction.LocalTransaction is
> keeping track of Addresses on which locks where acquired.
> That's surprising me .. why should it ever be interested in the
> specific Address? I'd expect it to be able to figure that out when
> needed, especially since the Address owning the lock might change over
> time I don't understand to track for a specific node.
This information is required at least here[1], but not sure wether we cannot rely on the
viewId which is now associated with every transaction to replace that logic.
[1] http://bit.ly/wgMIHH
_______________________________________________
infinispan-dev mailing list
infinispan-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/infinispan-dev
--
Manik Surtani
manik(a)jboss.org
twitter.com/maniksurtani
Lead, Infinispan
http://www.infinispan.org