Details
-
Feature Request
-
Resolution: Done
-
Major
-
None
-
None
-
Medium
Description
Allow a configuration attribute on <transaction /> to be able to specify whether cluster-wide locks are acquired eagerly or lazily. The current scheme (lazy) should be the default.
This could be implemented by broadcasting LockControlCommands alongside acquiring local locks for necessary keys.
Attachments
Issue Links
- is blocked by
-
ISPN-48 Introduce lock() and unlock() API methods
-
- Closed
-