-
Type:
Task
-
Resolution: Won't Do
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
Cluster Scalability
-
None
-
None
-
None
-
None
-
None
-
None
-
None
moveCollection is built on resharding, so with concurrency turned on it can run alongside reshardings of other collections.
Scenarios:
- start a resharding of A, then move an unrelated collection C onto a shard that is a donor or recipient for A
- move C while several reshardings are running, with overlapping donors and recipients
- move C while A is in its critical section, and start a resharding of A while C is in its critical section
- try to reshard or move a namespace that already has an operation in progress, and confirm it is still rejected
Assert that every operation completes, each collection ends up with exactly its own documents and the expected placement, and that no operation blocks another.