[ https://issues.apache.org/jira/browse/IGNITE-9322?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16685097#comment-16685097 ]
Ivan Pavlukhin edited comment on IGNITE-9322 at 11/13/18 12:01 PM: ------------------------------------------------------------------- Some points which are desirable: * Ability to break deadlock without a need to configure timeouts explicitly. * Negligible overhead of deadlock detection. Some unclear moments (possibly a subject for future improvements): * How to choose a victim transaction? was (Author: pavlukhin): Some points which are desirable: * Ability to break deadlock without a need to configure timeouts explicitly. * Negligible overhead of deadlock detection. Some unclear moments (possibly a subject for future improvements): * How to choose a victim transaction? > MVCC: implement deadlock detector > --------------------------------- > > Key: IGNITE-9322 > URL: https://issues.apache.org/jira/browse/IGNITE-9322 > Project: Ignite > Issue Type: Task > Components: mvcc > Reporter: Vladimir Ozerov > Assignee: Ivan Pavlukhin > Priority: Major > > Deadlocks are not uncommon during SQL execution. > We need to implement distributed deadlock detection protocol for MVCC. > Essentially, nodes should exchange some map of tx wait lists, and try to find > a loop. If loop is found, then one of problematic transactions should be > rolled back. -- This message was sent by Atlassian JIRA (v7.6.3#76005)