-
Type: Task
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: 3.7.1
-
Component/s: Sharding
-
Fully Compatible
-
Sharding 2018-03-12, Sharding 2018-04-09
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.
- depends on
-
SERVER-34145 Persist DB version on primary
- Closed
- is depended on by
-
SERVER-33252 [passthrough testing] extend cluster catalog consistency hook to add checks for databaseVersion
- Closed
- related to
-
SERVER-43439 Make movePrimary wait for updates from the database refresh to be written before clearing the flag in the minOpTimeRecovery document
- Closed