[
https://issues.jboss.org/browse/ISPN-1519?page=com.atlassian.jira.plugin....
]
Dan Berindei resolved ISPN-1519.
--------------------------------
Fix Version/s: 5.1.0.CR2
5.1.0.FINAL
Resolution: Done
With ISPN-1581 fixed the commit command really is retried indefinitely so this issue is
also fixed.
Stale locks on adding a new node to a cluster
---------------------------------------------
Key: ISPN-1519
URL:
https://issues.jboss.org/browse/ISPN-1519
Project: Infinispan
Issue Type: Bug
Components: Locking and Concurrency
Affects Versions: 5.0.1.FINAL
Reporter: Erik Salter
Assignee: Dan Berindei
Fix For: 5.1.0.CR2, 5.1.0.FINAL
There is an issue with stale locks when a new node joins a running cluster.
There are three caches all using eagerLockSingleNode=true with the transaction running on
the primary data owner. The local locks for the affected keys are acquired, and the
prepare is sent to the backup owner. During this time, the new node is detected and joins
the cluster. The transaction times out waiting for the transaction lock, and a rollback
is attempted. Whereas the local keys are unlocked, the remotely-acquired locks never
release.
I have full trace log files at:
http://dl.dropbox.com/u/10929737/5.0.1-stale-lock/data-grid-4/server.log....
http://dl.dropbox.com/u/10929737/5.0.1-stale-lock/data-grid-4/server.log....
http://dl.dropbox.com/u/10929737/5.0.1-stale-lock/data-grid-5/server.log....
The transaction in question is GlobalTransaction:<data-grid-4-61247>:169901, found
on data-grid-4. I have verified that the primary owner of the keys in question are on
data-grid-4.
--
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