Details
Description
As deadlock detection introduce overhead during transaction processing some configuration means should be introduced. Following aspects should be addressed:
1. Turning detection on/off.
2. Adjusting a timeout before starting actual detection.
It is proposed to introduce single property in TransactionConfiguration to address both concerns.
Also it is desired that configuration is consistent across all cluster nodes (detection turned off on even one node can lead to undetected deadlocks).
Attachments
Attachments
Issue Links
- is related to
-
IGNITE-11020 Document edge-chasing deadlock detection
- Open
-
IGNITE-9322 MVCC: implement deadlock detector
- Resolved
- links to