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
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

Once dropping the spill table can no longer transiently fail with ObjectIsBusy, we can remove the retry loop.

depends on

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

Needs Scheduling

related to

SERVER-103273 Drop SpillTable from spill engine on destruction

Closed

SERVER-107062 Update TODO in StorageEngineImpl::dropSpillTable

Closed

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

Created:: Jul 02 2025 05:32:27 PM UTC
Updated:: Jul 02 2025 05:51:10 PM UTC