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

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 3.2.18, 3.4.11, 3.6.0-rc1
    • Affects Version/s: 3.2.13, 3.4.9
    • Component/s: Storage
    • None
    • Fully Compatible
    • ALL
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      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.

        1. drops_actually_remove_wt_files.js
          3 kB

            Assignee:
            Eric Milkie
            Reporter:
            Bruce Lucas (Inactive)
            Votes:
            4 Vote for this issue
            Watchers:
            30 Start watching this issue

              Created:
              Updated:
              Resolved: