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-03-16, Storage Execution 2026-03-30
CAR Domain/s:
None

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

We should never get a real write conflict when writing data to the sorter table in the container-based spiller, but it still may be able to happen due to cache pressure.

is related to

SERVER-122296 Remove idx parameter from SorterSpiller::spill/spillUnique

Closed

SERVER-122301 Handle write conflicts in container-based sorter spiller when merging spills

Closed

SERVER-118769 Add tests with write conflicts to primary-driven index build suites

In Progress

related to

SERVER-118845 Handle the sorter -> index table writeConflictRetry when keyBatchSize > 1

Closed

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

Created:: Feb 04 2026 02:51:44 PM UTC
Updated:: Mar 26 2026 08:46:54 AM UTC
Resolved:: Mar 21 2026 02:17:29 PM UTC

Details

Description

Attachments

Issue Links

Activity

People

Dates