[SERVER-53793] Create concurrency workloads for tenant migrations Created: 14/Jan/21 Updated: 25/Mar/21 Resolved: 25/Mar/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Judah Schvimer | Assignee: | Jason Zhang |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | pm-1791_non-cloud-blocking, pm-1791_other_required | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Sprint: | Sharding 2021-03-08, Sharding 2021-03-22, Sharding 2021-04-05 |
| Participants: |
| Description |
|
Create a concurrency workload that runs donor commands concurrently (i.e. donorStartMigration, donorAbortMigration, and donorForgetMigration) with or without a real recipient to catch deadlocks/concurrency bugs |
| Comments |
| Comment by Jason Zhang [ 25/Mar/21 ] |
|
To be able to run any of the tenant migration commands, we need to start two replica sets. It may not be worth the effort to write a whole new fixture and suite to support tenant migrations since only cloud will be able to run these commands, so closing this ticket instead. |