[SERVER-83214] Handle direct connection database and collection registration on upgrade from RS Created: 14/Nov/23 Updated: 24/Nov/23 |
|
| Status: | Backlog |
| Project: | Core Server |
| Component/s: | Sharding, Upgrade/Downgrade |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Kaloian Manassiev | Assignee: | Backlog - Catalog and Routing |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | 8.0-Make-All-Deployments-Sharded-Clusters | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||
| Assigned Teams: |
Catalog and Routing
|
||||||||||||||||||||
| Participants: | |||||||||||||||||||||
| Description |
|
The work in SERVER-79159 will handle the registration of unsharded collections when coming from 7.0 clusters. However, it will not address the case where the 7.0 cluster has come from upgrade of a 7.0 replica set (meaning with direct connections). This ticket is to implement the following procedure and integrate it properly with that of SERVER-79159 as described in upgrade step U5. |