[infinispan-issues] [JBoss JIRA] (ISPN-4693) Locks acquired before a partition will never be released

[Dan Berindei (JIRA)]

    [ https://issues.jboss.org/browse/ISPN-4693?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13010087#comment-13010087 ] 

Dan Berindei commented on ISPN-4693:
------------------------------------

I think this can only happen if B keeps seeing the cluster during the split, or at least doesn't manage to install a cache topology. Otherwise {{TransactionTable.cleanupStaleTransactions()}} would roll back txs originating from A.

> Locks acquired before a partition will never be released
> --------------------------------------------------------
>
>                 Key: ISPN-4693
>                 URL: https://issues.jboss.org/browse/ISPN-4693
>             Project: Infinispan
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 6.0.2.Final
>            Reporter: Erik Salter
>            Assignee: Dan Berindei
>             Fix For: 7.0.0.Final
>
>
> Consider the following case:
> 1. A prepares a transaction for key K on nodes B and C.  
> 2. The primary owner B acquires and registers this lock.
> 3. The cluster partitions and A,C remain in partition one, and B in a separate partition.
> 4.  The transaction rolls back.  However, since B left the cluster, the rollback will not be sent to B.
> 5.  B rejoins the cluster.  It still has a lock acquired for key K.
> This can lead to a lock being acquired indefinitely.  



--
This message was sent by Atlassian JIRA
(v6.3.1#6329)