-
Type: Bug
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: None
-
Cluster Scalability
-
Fully Compatible
-
ALL
-
v8.0, v7.0, v6.0, v5.0
-
Cluster Scalability 2024-4-29
-
3
The transaction router only takes into account the afterClusterTime and the latest known vector clock time when selecting the atClusterTime setting:
- is related to
-
SERVER-79763 Default read concern setting is not being applied to TransactionRouter
- Backlog
-
SERVER-78949 Consider folding atClusterTime into readConcern object in TransactionRouter::SharedTransactionOptions
- Backlog
- related to
-
SERVER-79437 Providing an explicit atClusterTime with read concern snapshot in a transaction can violate snapshot isolation.
- Closed
-
SERVER-89865 Complete TODO listed in SERVER-79766
- Closed