[SERVER-76507] Write Concurrency Test for movePrimary on Single Collection Database Created: 25/Apr/23 Updated: 01/Jun/23 Resolved: 01/Jun/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | New Feature | Priority: | Major - P3 |
| Reporter: | Brett Nawrocki | Assignee: | [DO NOT USE] Backlog - Sharding NYC |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | sharding-nyc-subteam1 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Sharding NYC
|
||||||||
| Participants: | |||||||||
| Description |
|
Write a js concurrency test which performs ordinary CRUD ops (no transactions) on a single collection database while that database is being moved via movePrimary. If possible, modify the existing crud op concurrency test to work under the initial restrictions (see |