-
Type: Bug
-
Resolution: Won't Fix
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
ALL
-
Execution Team 2023-02-20
-
135
In WT-10576 we found that the way we currently drop temporary collections can lead to invalid memory access. To hit this failure the following must be true:
- Operation A has a WT transaction open and has modified collection C
- Collection C is dropped
- Operation A performs a commit/rollback
This is mostly an issue with multi-document transactions but it could be a problem in general. We should either defer the drop until after the commmit/rollback takes place so we don't access invalid memory.
- is related to
-
SERVER-74085 Ensure queries that spill to TemporaryRecordStores checkpoint their data
- Backlog
-
WT-10576 Return EBUSY on forced drop if there is an active transaction
- Closed