[SERVER-86309] Untrack unsplittable collections on downgrade Created: 06/Feb/24 Updated: 07/Feb/24 |
|
| Status: | Needs Scheduling |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Marcos José Grillo Ramirez | Assignee: | Backlog - Catalog and Routing |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | PM-3364-Milestone-4 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Catalog and Routing
|
||||||||
| Participants: | |||||||||
| Description |
|
This branch contains work in progress on the setFeatureCompatibility command that tracks unsharded collections on upgrade, and untrack collections on downgrade. The new plan for 8.0 do not require tracking all unsharded collections, considering that now they will be lazily tracked by moveCollection. However, we still need the dowgrade code, and the coordinator that was already developed there. The purpose of this ticket is to get the work necessary regarding fcv downgrade from the forementioned branch for 8.0. |