Details
-
Bug
-
Resolution: Unresolved
-
Major - P3
-
None
-
None
-
None
-
Cluster Scalability
-
ALL
-
3
Description
The transaction router only takes into account the afterClusterTime and the latest known vector clock time when selecting the atClusterTime setting:
Attachments
Issue Links
- 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
-