[infinispan-dev] Keeping track of locked nodes

[Mircea Markus]

> One potential problem with this design is when we have a transaction
> prepared on the old primary, and the new primary owner is a cache
> that
> just started. The new cache won't have any prepared transactions, so
> no "backup locks" to prevent new transactions from acquiring the
> lock.
> I'm pretty sure this issue has come up in our discussions before, but
> I can't remember how we decided to handle it.
I don't rememebr disscussing it but good point.
The new owner-node being up means that state transfer is finished. State transfe won't start before the locks on the previous-owner are released, so there shouldn't be any locking issue. Unless I'm wrong :) 

> Mircea, perhaps an update of
> https://community.jboss.org/wiki/SingleNodeLockingModel is in order?
> ;-)
yes, I''ll update the docs.