[SERVER-79766] TransactionRouter ignores atClusterTime setting in the request Created: 04/Aug/23  Updated: 12/Dec/23

Status: Backlog
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Randolph Tan Assignee: Backlog - Cluster Scalability
Resolution: Unresolved Votes: 0
Labels: cs-subteam1, sharding-nyc-subteam1
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-79437 Providing an explicit atClusterTime w... Closed
is related to SERVER-79763 Default read concern setting is not b... Backlog
is related to SERVER-78949 Consider folding atClusterTime into r... Backlog
Assigned Teams:
Cluster Scalability
Operating System: ALL
Participants:
Story Points: 3

 Description   

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


Generated at Thu Feb 08 06:41:50 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.