Loading...

XML

Word

Printable

JSON

Type: Engineering Test
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-25
CAR Domain/s:
None

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

For any tests that couldn't test the write conflict failpoint due to it not being storage engine agnostic, we can enable some more unit testing to exercise write conflict handling! woooohoooo

depends on

SERVER-126328 Have a storage engine-agnostic way to turn on write conflict fail points in unit tests

Closed

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

Closed

related to

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:: Stephanie Eristoff
Participants:: Githook User, Stephanie Eristoff
Votes:: 0 Vote for this issue
Watchers:: 3 Start watching this issue

Created:: May 11 2026 01:27:58 PM UTC
Updated:: May 21 2026 09:42:19 PM UTC
Resolved:: May 21 2026 09:31:52 PM UTC

Details

Description

Attachments

Issue Links

Activity

People

Dates