[SERVER-64344] Do not use atClusterTime when refreshing routing table on config server Created: 09/Mar/22  Updated: 29/Oct/23  Resolved: 14/Mar/22

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 6.0.0-rc0

Type: Task Priority: Major - P3
Reporter: Tommaso Tocci Assignee: Tommaso Tocci
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Sprint: Sharding EMEA 2022-03-21
Participants:

 Description   

Currently on each collection refresh performed by a node of the CSRS we perform an aggregation with a snapshotReadConcern with an atClusterTime equal to the last locally applied optime. This means that every time we perform a collection refresh we will need to wait for the latest applied op time to be majority committed before we can take the snapshot.

Instead we could simply use a snapshotReadConcern without specifying any cluster time so that we will read from the latest committed snapshot.



 Comments   
Comment by Githook User [ 14/Mar/22 ]

Author:

{'name': 'Tommaso Tocci', 'email': 'tommaso.tocci@mongodb.com', 'username': 'toto-dev'}

Message: SERVER-64344 Do not use atClusterTime when refreshing routing table on config server
Branch: master
https://github.com/mongodb/mongo/commit/960a4440e82f1fb274f0c4cb01dbda16c866cf88

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