[jbosscache-issues] [JBoss JIRA] Commented: (JBCACHE-1494) Lock-per-Fqn option in addition to lock striping, for MVCC
[
https://jira.jboss.org/jira/browse/JBCACHE-1494?page=com.atlassian.jira.p...
]
Manik Surtani commented on JBCACHE-1494:
----------------------------------------
Lock striping can now be optionally disabled. It is enabled by default, as it is still
the preferred approach for most use cases.
To disable:
<locking .... useLockStriping="false" />
Configuration.setUseLockStriping(false);
Note that this config setting is only used if node locking scheme is MVCC. Also,
concurrencyLevel is meaningless and ignored if lock striping is false.
Lock-per-Fqn option in addition to lock striping, for MVCC
----------------------------------------------------------
Key: JBCACHE-1494
URL: https://jira.jboss.org/jira/browse/JBCACHE-1494
Project: JBoss Cache
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Locking
Affects Versions: 3.0.3.GA
Reporter: Manik Surtani
Assignee: Manik Surtani
Fix For: 3.1.0.GA
Lock striping, while performant and memory efficient, can lead to deadlocks in certain
cases where several fqns map to the same lock. An alternative where a lock er fqn is used
may be desirable.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira