[SERVER-37568] computeAtClusterTimeForOneShard should always return the latest logical clock time Created: 11/Oct/18  Updated: 29/Oct/23  Resolved: 12/Oct/18

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: 4.1.5

Type: Task Priority: Major - P3
Reporter: Jack Mulrow Assignee: Jack Mulrow
Resolution: Fixed Votes: 0
Labels: ShardedTxn:GlobalSnapshot
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-36312 Re-enable atClusterTime selection alg... Closed
Backwards Compatibility: Fully Compatible
Sprint: Sharding 2018-10-22
Participants:

 Description   

Currently when mongoS chooses an atClusterTime for queries it knows targets only one shard, it will choose the latest lastCommitted opTime timestamp it has seen from the shard. This will eventually be changed to use the latest lastApplied opTime timestamp to leverage speculative snapshot behavior, but until then, to enable testing of transactions on single shards with enableMajorityReadConcern=false, the computed time should instead always be the latest time in the router's logical clock. This matches the existing behavior for writes and for reads that target multiple shards.



 Comments   
Comment by Githook User [ 12/Oct/18 ]

Author:

{'name': 'Jack Mulrow', 'email': 'jack.mulrow@mongodb.com', 'username': 'jsmulrow'}

Message: SERVER-37568 computeAtClusterTimeForOneShard should always return the latest logical clock time
Branch: master
https://github.com/mongodb/mongo/commit/efd0d5bd565b5edba222057da24287d08c19056e

Generated at Thu Feb 08 04:46:22 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.