Loading...

XML

Word

Printable

JSON

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

Assigned Teams:

Storage Execution
Backwards Compatibility:
Fully Compatible
Sprint:
Storage Execution 2026-05-11, Storage Execution 2026-05-25
CAR Domain/s:
None

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

There are existing fail points that can artificially inject write conflicts, but it's difficult to use them for unit tests because they're WT-specific. We should have a storage engine-agnostic way to turn them on in unit tests, possibly using the RecordStoreHarnessHelper or something similar.

is depended on by

SERVER-126385 Make unit tests that exercise _writeStateToContainer write conflict retry

Closed

related to

SERVER-126415 Expand unit-test coverage of write-conflict injection using enableWriteConflictForWrites

Backlog

SERVER-124273 Test recordDuplicateKey writeConflictRetry in primary-driven index builds

Closed

SERVER-127270 Test drainBackgroundWrites batch retry under write conflict in primary-driven index builds

Closed

SERVER-127369 Test deleteSorterEntriesOutsideRanges with a write conflict

Closed

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

Created:: May 08 2026 06:38:50 PM UTC
Updated:: May 21 2026 06:52:47 PM UTC
Resolved:: May 12 2026 12:29:44 AM UTC

Details

Description

Attachments

Issue Links

Activity

People

Dates