[infinispan-issues] [JBoss JIRA] Created: (ISPN-1007) eagerLockSingleNode="true" and rehasing

[Mircea Markus (JIRA)]

eagerLockSingleNode="true" and rehasing
---------------------------------------

                 Key: ISPN-1007
                 URL: https://issues.jboss.org/browse/ISPN-1007
             Project: Infinispan
          Issue Type: Bug
          Components: Transactions
    Affects Versions: 4.2.1.FINAL
            Reporter: Mircea Markus
            Assignee: Mircea Markus
             Fix For: 4.2.2.BETA1, 5.0.0.FINAL


When eagerLockSingleNode="true", if the main data owner of a key changes during a transaction then the k might end up in inconsistent state.
A solution to avoid this is:
- on topology change, if a eagerLockSingleNode is enabled, iterate over all transactions's keys
- if the main owner for a key has changed then just mark the tx for rollback

This way, on next operation for that transaction an exception should be thrown, e.g. TxRollbackOnlyException

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira