[infinispan-issues] [JBoss JIRA] Updated: (ISPN-860) Rehashing into a running cluster causes lock timeouts and lock cleanup errors

Erik Salter (JIRA) jira-events at lists.jboss.org
Tue Jan 4 10:35:17 EST 2011


     [ https://issues.jboss.org/browse/ISPN-860?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Erik Salter updated ISPN-860:
-----------------------------

    Attachment: multinode-rehash.zip


> Rehashing into a running cluster causes lock timeouts and lock cleanup errors
> -----------------------------------------------------------------------------
>
>                 Key: ISPN-860
>                 URL: https://issues.jboss.org/browse/ISPN-860
>             Project: Infinispan
>          Issue Type: Bug
>            Reporter: Erik Salter
>            Assignee: Manik Surtani
>         Attachments: multinode-rehash.zip
>
>
> We are seeing some severe issues with a new node joining a cluster running transactions.  Specifically, when a new node added to the system, some transactions running against the previous nodes will fail due to locks never being released.  There will be a lot of lock timeouts as well.
> All of our caches are in DIST mode.  The number of owners is 3.  We are also making liberal use of the new "eagerLockSingleNode" flag.
> The attached test case illustrates the lock timeout problem.  

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

        


More information about the infinispan-issues mailing list