[SERVER-83397] Introduce new suites with unsharded collections and the balancer enabled Created: 17/Nov/23 Updated: 07/Feb/24 |
|
| 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: | PM-3364-Milestone-4 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Catalog and Routing
|
| Participants: |
| Description |
|
The *_with_balancer suites (eg. concurrency_sharded_replication_with_balancer) run the balancer in the background for suites with sharded collections. Once the balancer also distributes unsharded collections, we should introduce new *_with_balancer suites that have unsharded collections and the balancer enabled. This should also extend the `balancerShouldReturnRandomMigrations` failpoint so that the fsm workloads will run with random moveCollection commands in the background. |