You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ignite.apache.org by "Ivan Pavlukhin (JIRA)" <ji...@apache.org> on 2019/01/22 14:34:00 UTC

[jira] [Created] (IGNITE-11029) Public API for edge-chasing deadlock detection configuration

Ivan Pavlukhin created IGNITE-11029:
---------------------------------------

             Summary: Public API for edge-chasing deadlock detection configuration
                 Key: IGNITE-11029
                 URL: https://issues.apache.org/jira/browse/IGNITE-11029
             Project: Ignite
          Issue Type: Task
          Components: mvcc
            Reporter: Ivan Pavlukhin
             Fix For: 2.8


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 items.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)