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

Erik Salter (JIRA) issues at jboss.org
Thu Sep 4 16:07:59 EDT 2014


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

Erik Salter commented on ISPN-4693:
-----------------------------------

A simple, brute-force solution is to periodically walk the TransactionTable and compare the active transaction to its creation time.  Any transaction that is greater than txTimeout and not completed would be rolled back.  (CacheTransaction, etc, would need a field for creation time, which is trivial to add).



> 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
>
> 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)


More information about the infinispan-issues mailing list