[SERVER-70687] Set the initial content of config.placementHistory on FCV upgrade Created: 19/Oct/22  Updated: 29/Oct/23  Resolved: 30/Jan/23

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 6.3.0-rc0

Type: Task Priority: Major - P3
Reporter: Paolo Polato Assignee: Enrico Golfieri
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
is depended on by SERVER-72870 Serialise the handling of config.plac... Closed
Related
related to SERVER-73343 Optimize the aggregation pipeline tha... Closed
Assigned Teams:
Sharding EMEA
Backwards Compatibility: Fully Compatible
Sprint: Sharding EMEA 2023-01-23, Sharding EMEA 2023-02-06
Participants:

 Description   

With the introduction of a new config.placementHistory collection into the sharding catalog, the FCV upgrade process will need to take the appropriate steps to ensure that its content will be consistent.

More specifically, the config server will have to generate a placement entry for each existing namespace (database/collection) based on a snapshot of config.databases, config.collections and config.chunks.



 Comments   
Comment by Githook User [ 30/Jan/23 ]

Author:

{'name': 'Paolo Polato', 'email': 'paolo.polato@mongodb.com', 'username': 'ppolato'}

Message: SERVER-70687 Set the initial content of config.placementHistory on FCV upgrade
Branch: master
https://github.com/mongodb/mongo/commit/0e2dc4700e76e3815d4dd9f166cf518b1caf06b0

Generated at Thu Feb 08 06:16:50 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.