[
https://issues.jboss.org/browse/ISPN-1106?page=com.atlassian.jira.plugin....
]
Erik Salter commented on ISPN-1106:
-----------------------------------
More updates:
Running 50 threads against the production environment gives a lot of errors, and makes the
cache unusable (i.e it doesn't recover). The test was start node 1, start the test,
and then start node 2
These are large files, but you can get a sense of what's happening from the first
part.
http://dl.dropbox.com/u/10929737/5.0.0.CR3/server_node1.log
http://dl.dropbox.com/u/10929737/5.0.0.CR3/server_node2.log
Rehashing into a running cluster causes shared processing lock
contention
-------------------------------------------------------------------------
Key: ISPN-1106
URL:
https://issues.jboss.org/browse/ISPN-1106
Project: Infinispan
Issue Type: Bug
Affects Versions: 5.0.0.CR2
Reporter: Erik Salter
Assignee: Manik Surtani
Attachments: cacheTest.zip
On our initial test of 5.0.0.CR2, we wanted to test the cluster's rehashing
behavior/performance and if all locks were cleaned up.
The test was to start two nodes, then add a third node, all the while issuing commands to
it.
Upon adding a third node, the cluster becomes inoperable. The stack traces is in the
following location:
http://dl.dropbox.com/u/10929737/5.0.0.CR2/server_node1.log,
http://dl.dropbox.com/u/10929737/5.0.0.CR2/server_node2.log,
http://dl.dropbox.com/u/10929737/5.0.0.CR2/server_node3.log
--
This message is automatically generated by JIRA.
For more information on JIRA, see:
http://www.atlassian.com/software/jira