-
Type:
Task
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
Cluster Scalability
-
ClusterScalability 26Oct-9Nov, ClusterScalability 9Nov-23Nov
-
None
-
None
-
None
-
None
-
None
-
None
-
None
currently the only hook that starts resharding code paths is add_remove_shards.py and it is included by various suites to run as a background hook. that test hook itself expects/tolerates ReshardCollectionInProgress , and the various tests in the suites that run alongside it also tolerate ReshardCollectionInProgress and ConflictingOperationInProgress (some locally, others via shell overrides).
This ticket should
- relax the toleration and update the handled errors to be the capped reshardings
- make the resharding code paths that run in the hook as concurrent as possible
- related to
-
SERVER-138508 Change error code for multiple reshardings to reflect maximum reshardings reached
-
- Backlog
-