Loading...

XML

Word

Printable

JSON

Type: Task
Resolution: Fixed
Priority: Major - P3
Fix Version/s: 8.2.0-rc1, 8.3.0-rc0
Affects Version/s: None
Component/s: None
Labels:
None

Assigned Teams:

Storage Execution
Backwards Compatibility:
Fully Compatible
Backport Requested:

v8.2
Sprint:
Storage Execution 2025-07-21, Storage Execution 2025-08-04
Confidence Status:
None
Work Order:
3
Size Category:
TBD
CAR Domain/s:
None

Aha! Reference:
None
Tracking Level:
None
Risk Status:
None
Exec Notes:
None
Goal Name(s):
None
Goal Link:
None

By truncating the spill table before dropping it, we can ensure that shutdown won't have to do any work to checkpoint that data.

depends on

SERVER-106624 Truncate without first checking whether table is empty

Closed

SERVER-107652 Ensure that spill table doesn't hold open storage snapshot across API calls

Closed

SERVER-107753 Use "read uncommitted" isolation for spill table reads

Closed

related to

WT-14852 WT_SESSION::drop can incorrectly return EBUSY due to WT_UNCOMMITTED_DATA

Closed

SERVER-103273 Drop SpillTable from spill engine on destruction

Closed

Assignee:: Gregory Noma
Reporter:: Gregory Noma
Participants:: Githook User, Gregory Noma
Votes:: 0 Vote for this issue
Watchers:: 4 Start watching this issue

Created:: Jun 23 2025 08:12:22 PM UTC
Updated:: Jul 29 2025 08:32:45 PM UTC
Resolved:: Jul 23 2025 09:20:45 PM UTC
Confidence Status Last Update:: 22/Jul/25 3:22 PM