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

Remove wait for drop to have pending X lock in abort_transaction_thread_does_not_block_on_locks.js

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 4.0.6, 4.1.7
    • Component/s: Replication
    • Labels:
      None
    • Backwards Compatibility:
      Fully Compatible
    • Operating System:
      ALL
    • Backport Requested:
      v4.0
    • Sprint:
      Repl 2019-01-14
    • Linked BF Score:
      3

      Description

      This test starts two transactions. It then starts a collection drop, which will block behind the transactions. It confirms the drop has a pending X lock by running find commands until one times out. Finally, it waits for the transactions to expire and the drop to succeed (transactionLifetimeLimitSeconds was reduced to 10).

      However, depending on the timing of the test, it is possible for the find command not to run until the transactions are about to expire, in which case it can error with QueryPlanKilled when the collection is dropped.

      We can just remove the wait for the drop to have a pending X lock. No future test operations rely on the test having a pending X lock. Its purpose is just to confirm that the drop is blocked behind the transactions. However, this can be inferred from the namespaces.

        Attachments

          Activity

            People

            Assignee:
            tess.avitabile Tess Avitabile
            Reporter:
            tess.avitabile Tess Avitabile
            Participants:
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: