[infinispan-issues] [JBoss JIRA] Updated: (ISPN-518) Deadlock detection should be able to used with eager locking
[
https://jira.jboss.org/browse/ISPN-518?page=com.atlassian.jira.plugin.sys...
]
Mircea Markus updated ISPN-518:
-------------------------------
Attachment: eager_locking_work.patch
Patch with eager locking enabled.
Work that still needs to be done:
- parametrize LockingInterceptor.visitLockControlCommand to only do a remote-lock-first
if DLD is enabled
- if remotelock is successful and local lock fails, do a remote unlock (no such command as
yet, needs to be implemented)
Deadlock detection should be able to used with eager locking
------------------------------------------------------------
Key: ISPN-518
URL: https://jira.jboss.org/browse/ISPN-518
Project: Infinispan
Issue Type: Feature Request
Components: Locking and Concurrency
Affects Versions: 4.0.0.Final
Reporter: Erik Salter
Assignee: Mircea Markus
Fix For: 5.1.0.Final
Attachments: eager_locking_work.patch
(As described on the forums):
With a cache that explicitly (eagerly) locks a key and deadlock detecting --
If transactions operating on a different node try to lock the same key, Infinispan will
detect the deadlock. However, it can't interrupt the deadlock, so the transaction
ends up timing out.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira