[
https://issues.jboss.org/browse/ISPN-4108?page=com.atlassian.jira.plugin....
]
Dan Berindei commented on ISPN-4108:
------------------------------------
Note that the lock command is sometimes created in
{{PessimisticLockingInterceptor.acquireRemoteIfNeeded()}}, which is called by
PessimisticLockingInterceptor.visitPutKeyValueCommand/visitRemoveCommand/visitReplaceCommand/visitGetKeyValueCommand.
Pessimistic tx for a union CH will not be forwarded to all owners.
------------------------------------------------------------------
Key: ISPN-4108
URL:
https://issues.jboss.org/browse/ISPN-4108
Project: Infinispan
Issue Type: Bug
Components: State Transfer
Affects Versions: 5.2.7.Final
Reporter: Erik Salter
Assignee: Dan Berindei
There is a case where transactions originating from a LockControlCommand will not be
forwarded to the new owner during state transfer.
If the transactions begin on the old primary owner after the tx list was sent to the new
owner, the lock information may not be replicated to the joiner because the originator is
still the primary owner in the union CH that we use during state transfer. When state
transfer ends and the joiner becomes the new primary owner, it will allow other txs to
lock the same key. This leads to data loss/inconsistency.
We should change PessimisticLockingInterceptor to replicate the lock command to the other
owners even if the originator is the primary owner when there is a state transfer in
progress.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira