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

Two-phase drop can prevent subsequent transaction from acquiring locks.

    • Type: Icon: Bug Bug
    • Resolution: Duplicate
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: 4.0.0-rc4
    • Component/s: None
    • None
    • ALL

      Version 4.1.0-353-gc741174b3. Running a C Driver test that does the following:

      • Drop a collection called "test", ignore errors if the collection doesn't exist
      • Call {create: "test"}
      • With a new lsid and txnNumber, insert a document into "test"
      • Expected: success, the transaction is started and the document is inserted
      • Actual: "Unable to acquire lock ' {7905466228821833060: Database, 987937201180751204}

        ' within a max lock request timeout of '5ms' milliseconds."

      Same in 4.0.0-rc4. Works if I do not drop the collection immediately beforehand.

            Assignee:
            dianna.hohensee@mongodb.com Dianna Hohensee (Inactive)
            Reporter:
            jesse@mongodb.com A. Jesse Jiryu Davis
            Votes:
            0 Vote for this issue
            Watchers:
            10 Start watching this issue

              Created:
              Updated:
              Resolved: