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

WT table not dropped after collection is dropped due to long-running OperationContext

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: 3.2.13, 3.4.9
    • Fix Version/s: 3.2.18, 3.4.11, 3.6.0-rc1
    • Component/s: Storage
    • Labels:
      None
    • Backwards Compatibility:
      Fully Compatible
    • Operating System:
      ALL
    • Backport Completed:
    • Case:

      Description

      In a replica set

      • create a collection by inserting a document
      • restart the replica set
      • then drop the collection or database

      On the primary the corresponding WT tables will be dropped, but on the secondaries the index table will be dropped but not the collection table - the .wt file will remain, and the ftdc data will show a steady stream of 10 failed table drops per second.

        Attachments

          Issue Links

            Activity

              People

              • Votes:
                4 Vote for this issue
                Watchers:
                29 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: