-
Type:
Task
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
Storage Execution
-
Storage Execution 2026-03-16
-
None
-
None
-
None
-
None
-
None
-
None
-
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-118769 Add tests with write conflicts to primary-driven index build suites
-
- Open
-
- related to
-
SERVER-118845 Handle the sorter -> index table writeConflictRetry when keyBatchSize > 1
-
- Open
-