-
Type:
Task
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Schema Management
-
None
-
Storage Engines, Storage Engines - Foundations
-
SE Foundations - Q3+ Backlog
-
5
-
(copied to CRM)
-
0
MongoDB faces scenarios where it's expecting WiredTiger to drop a table, however, the table is left in a pending drop state. WiredTiger will prevent table drops for a variety of reasons, including:
- open cursors
- open backup cursors
- active transactions
- concurrent checkpoints
This ticket is to investigate the following mongo patch to identify the reasons why some tables are left in a pending drop state.
- is related to
-
SERVER-106835 Hanging drop-pending collections without holders in MongoDB 8.x
-
- Open
-
-
SERVER-106947 Infinite log messages after dropping database
-
- Open
-
-
SERVER-100890 Investigate uncommitted data during drop call
-
- Backlog
-
-
WT-14852 WT_SESSION::drop can incorrectly return EBUSY due to WT_UNCOMMITTED_DATA
-
- Closed
-
-
SERVER-100390 Add dump after failing drop
-
- Blocked
-