-
Type:
Task
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: None
-
None
-
Storage Execution
-
Fully Compatible
-
Storage Execution 2026-05-11, Storage Execution 2026-05-25, Storage Execution 2026-06-08
-
None
-
None
-
None
-
None
-
None
-
None
-
None
We should look into having "write conflict" versions of our jstest suites that run primary-driven index builds (like the existing stestfuzz_replication_write_conflicts suite).
- depends on
-
SERVER-124271 Sort spill merge can read freed WT cursor memory after a WriteConflictException
-
- Closed
-
-
SERVER-127279 Sorter's checksum calculator doesn't handle WCE
-
- Closed
-
-
SERVER-126155 Tolerate that WCE during load phase of primary driven index build can reset cursors inside the iterator
-
- Closed
-
-
SERVER-127613 Wrap logStartup in a writeConflictRetry
-
- Closed
-
-
SERVER-127614 Move commitBatch in BulkBuilderImpl::commit out of ON_BLOCK_EXIT
-
- Closed
-
- is related to
-
SERVER-128101 Fix intermittent TransientTransactionError failures in prepare-transaction index build tests under PDIB burn-in suite
-
- Closed
-
- related to
-
SERVER-127784 Add WTWriteConflictExceptionChance to the config fuzzer
-
- In Progress
-
-
SERVER-127598 Enable only setting the WTWriteConflictExceptionChance in enable_write_conflicts.js
-
- Closed
-
-
SERVER-118769 Add jstests with write conflicts to primary-driven index build suites
-
- Closed
-
-
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
-