[infinispan-issues] [JBoss JIRA] (ISPN-1343) Stale locks occurring on rehashing into a running cluster.
[
https://issues.jboss.org/browse/ISPN-1343?page=com.atlassian.jira.plugin....
]
Dan Berindei commented on ISPN-1343:
------------------------------------
Erik, I have increased the number of threads in the async transport pool and in the
JGroups OOB pool to 50 and I couldn't see the lock timeouts anymore.
Can you check if you can still reproduce them with these settings?
In the Infinispan configuration:
{code}
<asyncTransportExecutor>
<properties>
<property name="maxThreads" value="50"/>
</properties>
</asyncTransportExecutor>
{code}
In the JGroups configuration:
{code}
oob_thread_pool.max_threads="50"
{code}
Stale locks occurring on rehashing into a running cluster.
----------------------------------------------------------
Key: ISPN-1343
URL: https://issues.jboss.org/browse/ISPN-1343
Project: Infinispan
Issue Type: Bug
Components: Distributed Cache
Affects Versions: 5.0.0.FINAL
Reporter: Erik Salter
Assignee: Dan Berindei
Fix For: 5.0.1.FINAL, 5.1.0.ALPHA1, 5.1.0.FINAL
Attachments: ISPN-5-stale-lock.zip, ISPN-5-test-rehash.zip, RehashTest.java,
RehashTest.java
There is a stale lock issue that occurs when a client thread requests the same set of
eagerly-locked keys across a rehash. Attached is a unit test that can reproduce the
issue.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira