Loading...

XML

Word

Printable

JSON

Type: Bug
Resolution: Fixed
Priority: Major - P3
Fix Version/s: 8.1.0-rc0, 8.0.0-rc4, 7.0.13
Affects Version/s: None
Component/s: None
Labels:
- 8
- cs-subteam3

Assigned Teams:

Cluster Scalability
Backwards Compatibility:
Fully Compatible
Operating System:
ALL
Backport Requested:

v8.0, v7.0, v6.0, v5.0
Sprint:
Cluster Scalability 2024-4-29
Story Points:
3
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

The transaction router only takes into account the afterClusterTime and the latest known vector clock time when selecting the atClusterTime setting:

https://github.com/10gen/mongo/blob/c4fee3d918dd98c3cf07eee62fb8049cb4de4e21/src/mongo/s/transaction_router.cpp#L874

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

Assignee:: Cheahuychou Mao
Reporter:: Randolph Tan
Participants:: Cheahuychou Mao, Githook User, Randolph Tan
Votes:: 0 Vote for this issue
Watchers:: 9 Start watching this issue

Created:: Aug 04 2023 08:43:39 PM UTC
Updated:: Jul 23 2024 08:46:14 PM UTC
Resolved:: Apr 25 2024 03:38:09 PM UTC
Confidence Status Last Update:: 22/Apr/24 2:19 PM