Loading...

XML

Word

Printable

JSON

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

Backwards Compatibility:
Fully Compatible
Sprint:
Sharding 2018-04-09, Sharding 2018-04-23
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

After the config server's FCV changes from 3.6 to 4.0, it will start tracking history. As part of the upgrade/downgrade process we should call into all shards and cause them to invalidate their metadata cache so they pick up or drop the history.

depends on

SERVER-33781 Upgrade/downgrade the chunks history on FCV change

Closed

SERVER-34459 Clear in-memory database versions on setFCV downgrade on shard primaries and secondaries

Closed

is depended on by

SERVER-33356 Ensure shards' persisted collection cache picks up collection UUIDs after setFCV=4.0

Closed

related to

SERVER-34460 Mongos will not pick up database versions for database entries it already has cached after setFCV 4.0

Closed

Assignee:: Martin Neupauer (Inactive)
Reporter:: Kaloian Manassiev
Participants:: Githook User, Gregory McKeon, Kaloian Manassiev, Martin Neupauer
Votes:: 0 Vote for this issue
Watchers:: 5 Start watching this issue

Created:: Mar 09 2018 05:25:40 PM UTC
Updated:: Oct 29 2023 10:33:56 PM UTC
Resolved:: Apr 16 2018 10:15:31 PM UTC
Confidence Status Last Update:: 13/Apr/18 2:58 PM

Details

Description

Attachments

Issue Links

Forms

Activity

People

Dates