[SERVER-71168] Indexes on config server global indexes collections should be created during first FCV stage Created: 08/Nov/22 Updated: 29/Oct/23 Resolved: 15/Nov/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 6.2.0-rc0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Allison Easton | Assignee: | Allison Easton |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | PM-2583-Milestone-2 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Sharding EMEA 2022-11-14, Sharding EMEA 2022-11-28 |
| Participants: |
| Description |
|
Creating indexes on config.csrs.indexes changes the minimum collection timestamp for this collection. If the shard finishes FCV upgrade before these collection changes take place, the aggregation to get the global indexes from the config server will fail with SnapshotUnavailable. In order to prevent this, we should ensure that the config server has created the indexes before the shard can complete FCV upgrade. |
| Comments |
| Comment by Githook User [ 15/Nov/22 ] |
|
Author: {'name': 'Allison Easton', 'email': 'allison.easton@mongodb.com', 'username': 'allisoneaston'}Message: |