Loading...

XML

Word

Printable

JSON

Type: Task
Resolution: Duplicate
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
Linked BF Score:
200
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

Since spill table users can create multiple at a time, we may need to make sure that storage snapshots are never kept open across multiple API calls on the spill table. That way it cannot indefinitely interfere with another spill table being dropped.

duplicates

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

Closed

is depended on by

SERVER-106596 Truncate spill table before drop

Closed

SERVER-107034 Re-enable disabled query tests that spill in in-memory configurations

Closed

SERVER-107844 Re-enable featureFlagCreateSpillKVEngine

Closed

is related to

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

(1 related to)

Assignee:: Gregory Noma
Reporter:: Gregory Noma
Participants:: Gregory Noma
Votes:: 0 Vote for this issue
Watchers:: 3 Start watching this issue

Created:: Jul 16 2025 07:40:42 PM UTC
Updated:: Aug 01 2025 03:51:46 PM UTC
Resolved:: Jul 22 2025 01:57:45 PM UTC
Confidence Status Last Update:: 16/Jul/25 7:40 PM

Details

Description

Attachments

Issue Links

Forms

Activity

People

Dates