[SERVER-32608] Make secondaries refresh their database metadata from the persisted database cache Created: 09/Jan/18  Updated: 30/Oct/23  Resolved: 06/Apr/18

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: 3.7.1
Fix Version/s: 3.7.4

Type: Task Priority: Major - P3
Reporter: Randolph Tan Assignee: Janna Golden
Resolution: Fixed Votes: 0
Labels: todo_in_code
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-34145 Persist DB version on primary Closed
is depended on by SERVER-33252 [passthrough testing] extend cluster ... Closed
Related
related to SERVER-43439 Make movePrimary wait for updates fro... Closed
Backwards Compatibility: Fully Compatible
Sprint: Sharding 2018-03-12, Sharding 2018-04-09
Participants:

 Description   

We can do this by creating a 'config.cache.databases' collection on shards, and persisting the databaseVersion in it.

We also need to persist a 'refreshing' flag into the entry in 'config.cache.databases' when starting a refresh, and a 'refreshing=false' and 'lastDatabaseVersionRefreshed=<DatabaseVersion' flags on completing the refresh, and add OpObservers so that the secondary will invalidate its in-memory cache entry for the database.



 Comments   
Comment by Githook User [ 06/Apr/18 ]

Author:

{'email': 'golden.janna@gmail.com', 'name': 'jannaerin', 'username': 'jannaerin'}

Message: SERVER-32608 Make secondaries refresh their database metadata from the persisted database cache
Branch: master
https://github.com/mongodb/mongo/commit/47e4b6b791cce13a36ea499a9311d54f100412ee

Comment by Esha Maharishi (Inactive) [ 08/Mar/18 ]

SERVER-33252 is marked as depending on this, because the cluster catalog consistency hook will read config.cache.databases on the shards.

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