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

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major - P3
    • Resolution: Fixed
    • 3.2.13, 3.4.9
    • 3.2.18, 3.4.11, 3.6.0-rc1
    • Storage
    • None
    • Fully Compatible
    • ALL

    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

          duplicates

          Bug - A problem which impairs or prevents the functions of the product. SERVER-32082 dropDatabase reports success but db is still on disk of secondary

          • Major - P3 - Major loss of function.
          • Closed
          is duplicated by

          Bug - A problem which impairs or prevents the functions of the product. SERVER-31573 WT table not dropped on primary after collection is dropped

          • Major - P3 - Major loss of function.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. SERVER-33108 Collection deleted - file still exists

          • Major - P3 - Major loss of function.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. SERVER-34553 dropCollection does not free up storage on Secondary

          • Major - P3 - Major loss of function.
          • Closed
          is related to

          Bug - A problem which impairs or prevents the functions of the product. SERVER-26870 Sometimes collection data file is not removed even though collection is dropped

          • Major - P3 - Major loss of function.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. SERVER-31587 ReplBatcher has a long-running OperationContext

          • Major - P3 - Major loss of function.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. SERVER-31589 A primary's SyncSourceFeedback only renews an OperationContext on role changes.

          • Major - P3 - Major loss of function.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. SERVER-31590 WT yieldAndAwaitOplogDeletionRequest holds onto an OperationContext while blocking for an infrequent trigger

          • Major - P3 - Major loss of function.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. SERVER-31591 HMAC key refresh thread holds onto an OperationContext

          • Major - P3 - Major loss of function.
          • Closed
          related to

          Bug - A problem which impairs or prevents the functions of the product. SERVER-30426 dropDatabase very slow due to repeated calls to closeAllCursors

          • Major - P3 - Major loss of function.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. SERVER-31573 WT table not dropped on primary after collection is dropped

          • Major - P3 - Major loss of function.
          • Closed

          Improvement - An improvement or enhancement to an existing feature or task. SERVER-32030 SyncTail::oplogApplication uses a long-running OperationContext (3.2/3.4)

          • Major - P3 - Major loss of function.
          • Closed

          Activity

            People

              milkie@mongodb.com Eric Milkie
              bruce.lucas@mongodb.com Bruce Lucas (Inactive)
              Votes:
              4 Vote for this issue
              Watchers:
              30 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: