[BUG] Concurrent DbDeadlockTest blocks on CRDB

XMLWordPrintable

    • Type: Sub-task
    • Resolution: Fixed
    • Priority: L3 - Default
    • 7.14.0, 7.14.0-alpha2
    • Affects Version/s: None
    • Component/s: engine
    • None

      Given:
      Execute the DbDeadlockTest on CRDB.

      When:
      The tests tries to continue the test execution after a SELECT.

      Then:
      The test blocks the test thread and testing has to be stopped.

      Expected:

      • The test is executed only on DBs with TX isolation READ_COMMITTED.
      • A new (adjusted) test is provided only for CRDB with TX isolation SERIALIZABLE.

      Notes:

      • The test is designed to test a deadlock situation in a database with a READ_COMMITTED transaction isolation level.
      • Since CRDB uses a SERIALIZABLE level, and blocks READS when they encounter a concurrent write, the test logic produces a deadlock in CRDB.
      • In a real-life scenario the above wouldn't happen since one of the transactions would commit and unblock the waiting READ.

        This is the controller panel for Smart Panels app

              Assignee:
              Unassigned
              Reporter:
              Nikola Koevski
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

                Created:
                Updated:
                Resolved: