-
Type: Documentation
-
Resolution: Unresolved
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Storage Engines
-
3
-
StorEng - 2024-10-01, StorEng - 2024-10-15, StorEng - 2024-10-29, StorEng - 2024-11-12
The docs for WT_SESSION::drop state "This method requires exclusive access to the specified data source(s). If any cursors are open with the specified name(s) or a data source is otherwise in use, the call will fail and return EBUSY"
But it does not mention that EBUSY is also returned if the table has not yet been checkpointed.
The docs also don't mention the undocumented parameters "checkpoint_wait" and "lock_wait".
- is duplicated by
-
WT-13211 Document that WT_SESSION::drop can return EBUSY when data is not checkpointed
- Closed
- related to
-
SERVER-90075 dropIdent returning EBUSY during rollback_to_stable can crash server
- Closed