-
Type: Task
-
Resolution: Unresolved
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
Catalog and Routing
-
2
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 addZones and removeZones. 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.
- related to
-
SERVER-78918 Make `shardCollection` command shard authoritative
- Closed