-
Type:
Task
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: None
-
None
-
Catalog and Routing
-
Fully Compatible
-
CAR Team 2025-12-22, CAR Team 2026-01-05
-
200
-
None
-
None
-
None
-
None
-
None
-
None
-
None
In multi-doc transactions, the catalog write to modify the multikey fields is done in a side transaction on the primary. On the secondary, the multikey write happens with the user operation that causes the field to be set. This makes the writes have different timestamps.
In this ticket, we'll use the oplog entry generated from the side transaction to explicitly replicate the multikey write. Currently, the side transaction generates a no-op oplog entry. We might want to change it to a different type.
- duplicates
-
SERVER-113189 Aborted multi-doc transaction can leave inconsistent multikey fields within a replica set
-
- Closed
-
- is depended on by
-
-
- Closed
-
-
TOOLS-4039 Investigate changes in SERVER-114086: Explicitly replicate multikey writes in a multi-doc transaction
-
- Accepted
-
- related to
-
-
- Open
-