Loading...

XML

Word

Printable

JSON

Type: Task
Resolution: Fixed
Priority: Major - P3
Fix Version/s: 3.7.4
Affects Version/s: 3.7.1
Component/s: Sharding
Labels:
- todo_in_code

Backwards Compatibility:
Fully Compatible
Sprint:
Sharding 2018-03-12, Sharding 2018-04-09
Confidence Status:
None
Work Order:
3
CAR Domain/s:
None

Aha! Reference:
None
Tracking Level:
None
Risk Status:
None
Exec Notes:
None
Goal Name(s):
None
Goal Link:
None

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

Assignee:: Janna Golden
Reporter:: Randolph Tan
Participants:: Esha Maharishi, Githook User, Janna Golden, Randolph Tan
Votes:: 0 Vote for this issue
Watchers:: 3 Start watching this issue

Created:: Jan 09 2018 10:01:28 PM UTC
Updated:: Oct 30 2023 11:09:28 PM UTC
Resolved:: Apr 06 2018 11:08:09 PM UTC
Confidence Status Last Update:: 02/Apr/18 9:15 PM

Details

Description

Attachments

Issue Links

Activity

People

Dates