Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-38059

Transactions write conflicts tests should clean up any transactions on failure

    XMLWordPrintable

Details

    • Bug
    • Status: Closed
    • Major - P3
    • Resolution: Fixed
    • None
    • 4.0.6, 4.1.6
    • Replication
    • None
    • Fully Compatible
    • ALL
    • v4.0
    • Repl 2018-11-19, Repl 2018-12-03
    • 60

    Description

      The transactions_write_conflicts.js and transactions_write_conflicts_unique_indexes.js tests run multiple pairs of transactions with writes in various interleavings. In the case that a transaction operation fails for some reason and throws an exception, the test may fail but leave a transaction open. This can lead to problems if we subsequently try to run consistency checks, for example, that require taking strong collection locks. To help this, we should have these tests clean up after themselves in case an exception is thrown, by aborting all transactions or killing the sessions they were using.

      Attachments

        Issue Links

          Activity

            People

              william.schultz@mongodb.com William Schultz (Inactive)
              william.schultz@mongodb.com William Schultz (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: