Uploaded image for project: 'Ignite'
  1. Ignite
  2. IGNITE-11029

Public API for edge-chasing deadlock detection configuration

    XMLWordPrintableJSON

Details

    • Task
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • None
    • 2.8
    • mvcc
    • None
    • Docs Required, Release Notes Required

    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

        Issue Links

          Activity

            People

              Pavlukhin Ivan Pavlukhin
              Pavlukhin Ivan Pavlukhin
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Time Tracking

                  Estimated:
                  Original Estimate - Not Specified
                  Not Specified
                  Remaining:
                  Remaining Estimate - 0h
                  0h
                  Logged:
                  Time Spent - 1h
                  1h