Loading...

XML

Word

Printable

JSON

Type: Task
Resolution: Unresolved
Priority: Major - P3
Fix Version/s: None
Affects Version/s: None
Component/s: None
Labels:
None

Assigned Teams:

Storage Execution
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-107652 Ensure that spill table doesn't hold open storage snapshot across API calls

In Code Review

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

In Code Review

SERVER-106624 Truncate without first checking whether table is empty

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:: Gregory Noma
Votes:: 0 Vote for this issue
Watchers:: 3 Start watching this issue

Created:: Jun 23 2025 08:12:22 PM UTC
Updated:: Jul 21 2025 02:24:26 PM UTC
Confidence Status Last Update:: 25/Jun/25 1:03 AM