[SERVER-83880] Allow collection creation on the least loaded shard rather than the dbPrimary Created: 05/Dec/23 Updated: 06/Dec/23 |
|
| Status: | Backlog |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Allison Easton | Assignee: | Backlog - Catalog and Routing |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Catalog and Routing
|
| Participants: |
| Description |
|
If a data shard is not specified for a collection creation, the default is currently to choose the dbPrimary (sharded, unsharded). However, now that the balancer is moving unsharded collections and those collections can live outside the dbprimary, we can instead choose the least loaded shard by querying the balancer and use that as the data shard. We should still always choose the dbPrimary if unsharded collection balancing is disabled. |