Loading...

XML

Word

Printable

JSON

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

Assigned Teams:

Replication
Confidence Status:
None
Work Order:
3
CAR Domain/s:
None

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

It's hard to tell when diagnosing the root of a write conflict whether the mongodb layer transformed another error into a write conflict, or if the write conflict came from the storage engine, what the source of the write conflict is.

is related to

SERVER-76715 Log origin of WriteConflictException in writeConflictRetry()

Closed

related to

SERVER-76774 Invariant that secondary oplog application doesn't get prepare conflicts

Closed

Assignee:: Unassigned
Reporter:: Samyukta Lanka
Participants:: Samyukta Lanka
Votes:: 0 Vote for this issue
Watchers:: 9 Start watching this issue

Created:: Jul 20 2023 07:27:22 PM UTC
Updated:: Feb 10 2025 06:38:51 PM UTC

Details

Description

Attachments

Issue Links

Forms

Activity

People

Dates