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.
- duplicates
-
SERVER-32082 dropDatabase reports success but db is still on disk of secondary
- Closed
- is duplicated by
-
SERVER-31573 WT table not dropped on primary after collection is dropped
- Closed
-
SERVER-33108 Collection deleted - file still exists
- Closed
-
SERVER-34553 dropCollection does not free up storage on Secondary
- Closed
- is related to
-
SERVER-26870 Sometimes collection data file is not removed even though collection is dropped
- Closed
-
SERVER-31587 ReplBatcher has a long-running OperationContext
- Closed
-
SERVER-31589 A primary's SyncSourceFeedback only renews an OperationContext on role changes.
- Closed
-
SERVER-31590 WT yieldAndAwaitOplogDeletionRequest holds onto an OperationContext while blocking for an infrequent trigger
- Closed
-
SERVER-31591 HMAC key refresh thread holds onto an OperationContext
- Closed
- related to
-
SERVER-30426 dropDatabase very slow due to repeated calls to closeAllCursors
- Closed
-
SERVER-31573 WT table not dropped on primary after collection is dropped
- Closed
-
SERVER-32030 SyncTail::oplogApplication uses a long-running OperationContext (3.2/3.4)
- Closed