[infinispan-issues] [JBoss JIRA] Issue Comment Edited: (ISPN-1106) Rehashing into a running cluster causes shared processing lock contention

[ https://issues.jboss.org/browse/ISPN-1106?page=com.atlassian.jira.plugin.... ] Erik Salter edited comment on ISPN-1106 at 5/15/11 10:55 PM: ------------------------------------------------------------- As an update, I tested this behavior with the latest rehash changes from master. It's much better, but there are still issues with a DIST-mode cluster, eager lock single node, and 2 owners. For instance: - Start nodes 1 and 2. - Run a series of transactions against the cluster. - Start node 3. Repeat tests. There are some errors, but well within the expected behavior (i.e. not handling rollback exceptions in application code). - Stop node 2. Tests are still running. - Restart node 2. Here, I see that a bunch of failures happen due to locks held open on node 1. Node 2 was now the primary data owner. These locks are never released by node 1, even after the rehash. I'll see if I can't build a unit test to reproduce this. was (Author: an1310): As an update, I tested this behavior with the latest rehash changes from master. It's much better, but there are still issues with a DIST-mode cluster, eager lock single node, and 2 owners. For instance: - Start nodes 1 and 2. - Run a series of transactions against the cluster. - Start node 3. Repeat tests. There are some errors, but well within the expected behavior (i.e. not handling rollback exceptions in application code). - Stop node 2. Tests are still running. - Restart node 2. Here, I see that a bunch of failures happen due to locks held open on node 1. Node 2 was now the primary data owner. These locks are never released by node 1, even after the rehash. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira