Loading...

XML

Word

Printable

JSON

Type: Bug
Resolution: Unresolved
Priority: Major - P3
Fix Version/s: None
Affects Version/s: None
Component/s: None
Labels:
None

Assigned Teams:

Query Execution
Operating System:
ALL
CAR Domain/s:
None

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

SERVER-103347 was filed in 2025 in response to upsert operations that encounter write conflicts not respecting maxTimeMS. After some investigation, I confirmed this behavior was fixed as a side effect of ~~SERVER-66751~~. To protect against regressions, a JS test should be added.

is depended on by

SERVER-103347 Upsert operations does not respect maxTimeMS in the presence of a Write Conflict

In Progress

is related to

SERVER-103347 Upsert operations does not respect maxTimeMS in the presence of a Write Conflict

In Progress

SERVER-66751 Upsert stage should use generic yield machinery instead of writeConflictRetry

Closed

Assignee:: Unassigned
Reporter:: Kyle Burgess
Participants:: Kyle Burgess
Votes:: 0 Vote for this issue
Watchers:: 1 Start watching this issue

Created:: Sep 08 2026 08:58:01 PM UTC
Updated:: Sep 08 2026 09:02:06 PM UTC

Details

Description

Attachments

Issue Links

Activity

People

Dates

PagerDuty