[infinispan-dev] Keeping track of locked nodes

[Mircea Markus]

> >> Thinking some more the old-view approach should happen on C and it
> >> doesn't, so we're not covered.
> >> The soutions I see here is to either replay the prepare on C as
> >> part
> >> of the state transfer or not to release the ST lock until the
> >> transaction (vs the prepare command) is complete.
> 
> We've committed to implementing NBST for 5.2, so not releasing the ST
> lock is not an option.
Won't NBST solve this through lock migration? 
As 5.1.1 ships with blocking state transfer and this fix is for 5.1.1 only I think the solution mentioned above is also worth considering.