-
Type:
Task
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: None
-
None
-
Cluster Scalability
-
Fully Compatible
-
Cluster Scalability 2024-2-19, Cluster Scalability 2024-3-4, Cluster Scalability 2024-3-18, Cluster Scalability 2024-4-1
A transaction-ending error is thrown in additional participants when readConcern on a request does not match the transaction's readConcern.
During getMore, the readConcern can differ between router and shard, specifically in afterClusterTime.
Max notes that although readConcern is included in requests, compare-equal should only be enforced on the first statement of a transaction that the participant processes, not on subsequent statements of the transaction.
- is depended on by
-
SERVER-84470 Allow $lookup to target an unsplittable collection on a primary shard within a multi-document transaction
-
- Closed
-
-
-
- Closed
-