[SERVER-83388] Increase test coverage for concurrent create collection with addShard/removeShard Created: 17/Nov/23 Updated: 30/Nov/23 |
|
| Status: | Backlog |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Pol Pinol | Assignee: | Backlog - Catalog and Routing |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | robust-create-collection | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Catalog and Routing
|
||||||||
| Participants: | |||||||||
| Description |
|
With recent changes on the shardCollection and the inclusion of entering the critical section on the participants shards, this command must be robust to errors such as addShard and removeShard. These commands are not yet running concurrently on our testing, so I propose to increase the coverage by including (or expanding) an fsm test with that objective. |