[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: |
|
||||||||||||||||
| 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: |