-
Type: Task
-
Resolution: Unresolved
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
Cluster Scalability
-
Cluster Scalability Priorities
SERVER-89825 discovered that Timeseries testing of sharded collection didn’t actually move chunks in our balancer enabled suites.
This ticket is to audit all collection types to ensure that:
1. We have adequate coverage for each type
2. That coverage is actually functional
- related to
-
SERVER-89825 Investigate why jstests/concurrency/fsm_workloads/timeseries_mirrored_writes.js fails in case of concurrent moveCollection
- Closed