[SERVER-33783] Make shards and mongos do full routing/filtering metadata refresh after FCV change Created: 09/Mar/18  Updated: 29/Oct/23  Resolved: 16/Apr/18

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

Type: Task Priority: Major - P3
Reporter: Kaloian Manassiev Assignee: Martin Neupauer
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-33781 Upgrade/downgrade the chunks history ... Closed
depends on SERVER-34459 Clear in-memory database versions on ... Closed
is depended on by SERVER-33356 Ensure shards' persisted collection c... Closed
Related
related to SERVER-34460 Mongos will not pick up database vers... Closed
Backwards Compatibility: Fully Compatible
Sprint: Sharding 2018-04-09, Sharding 2018-04-23
Participants:

 Description   

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.



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

Author:

{'name': 'Martin Neupauer', 'email': 'martin.neupauer@mongodb.com', 'username': 'MartinNeupauer'}

Message: SERVER-33783 Make shards and mongos do full routing/filtering metadata refresh after FCV change
Branch: master
https://github.com/mongodb/mongo/commit/a58a24439b972bb8af00caf0cf6c0a8696a5899c

Comment by Gregory McKeon (Inactive) [ 16/Apr/18 ]

pinging martin.neupauer, does this still look possible for the end of the day?

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