Vladimir Ozerov created IGNITE-9411:
---------------------------------------
Summary: Lock: make sure lock timeouts works fine
Key: IGNITE-9411
URL: https://issues.apache.org/jira/browse/IGNITE-9411
Project: Ignite
Issue Type: Task
Components: mvcc
Reporter: Vladimir Ozerov
Fix For: 2.7
In SQL it is not uncommon that locks are taken in arbitrary order, what may
lead to deadlocks. Fair deadlock detector is good solution in monolithic
databases - just analyze dependency graph and kill one of conflicting
transactions.
We have a ticket to implement distributed deadlock detector in Ignite [1].
However, this solution is rather complex and may bring some overhead.
For now it is better to rely on some timeout (global or per-transaction), and
rollback TX when it fails to lock certain entry for a long time. Probably we
already have this feature in some form. Need to add verify that it works and
add more tests if needed.
[1] https://issues.apache.org/jira/browse/IGNITE-9322
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
