[SERVER-70132] Handle FCV transitions for global indexes info Created: 30/Sep/22 Updated: 29/Oct/23 Resolved: 31/Jan/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 6.3.0-rc0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Marcos José Grillo Ramirez | Assignee: | Allison Easton |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | PM-2583-Milestone-2 | ||
| 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 |
|
Currently, as part of FCV downgrade, we're dropping the global indexes collection. However, we shouldn't drop global indexes information if the user still has global indexes. Instead, we should abort downgrade with an error if the user tries to downgrade and still has global indexes. Once we are sure that the user has no global indexes, we still need to drop the global indexes collections, but we also need to clear the in memory state relating to global indexes in the CSR. |
| Comments |
| Comment by Githook User [ 01/Feb/23 ] |
|
Author: {'name': 'Allison Easton', 'email': 'allison.easton@mongodb.com', 'username': 'allisoneaston'}Message: |
| Comment by Githook User [ 30/Jan/23 ] |
|
Author: {'name': 'Allison Easton', 'email': 'allison.easton@mongodb.com', 'username': 'allisoneaston'}Message: |