[SERVER-49856] Make DatabaseCache causally consistent through the usage of ComparableDatabaseVersion Created: 24/Jul/20  Updated: 29/Oct/23  Resolved: 06/Aug/20

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

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

Issue Links:
Depends
depends on SERVER-48992 Implement database cache on top of Re... Closed
depends on SERVER-49189 Make the ReadThroughCache lookup send... Closed
Issue split
split from SERVER-48991 Make CatalogCache causally consistent Closed
Problem/Incident
causes SERVER-51390 Always refresh database cache on Stal... Closed
Backwards Compatibility: Fully Compatible
Sprint: Sharding 2020-08-10
Participants:

 Description   

Introduce a new class called say ComparableDatabaseVersion, which allows to compare two database versions that have different epoch. This class will be use as clock for the DatabaseCache (introduced by SERVER-48992) to make it causally consistent. In particular it will be use to advance the cached database entry's time as a result of a reception of StaleDatabaseVersion.



 Comments   
Comment by Tommaso Tocci [ 06/Aug/20 ]

Author:

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

Message: SERVER-48991 Make DatabaseCache causally consistent through the usage of ComparableDatabaseVersion
Branch: master
https://github.com/mongodb/mongo/commit/8714e192a893e9768fd4ab7d734de6a6ead941c1

Comment by Tommaso Tocci [ 06/Aug/20 ]

https://mongodbcr.appspot.com/659920001/

Generated at Thu Feb 08 05:21:02 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.