-
Type:
Task
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: None
-
None
-
Fully Compatible
-
v5.3
-
Sharding EMEA 2022-02-21, Sharding EMEA 2022-03-07
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Initially, the defragment_large_collection jstest ran on only one collection. We then increased this to 3 collections to ensure that we were testing concurrent defragmentations. However, we should really be checking both cases. In this ticket, we should run the defragment_large_collection twice, once with one collection and once with 3 collections. (And a third with a random number?)