-
Type: Improvement
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: None
-
None
-
Storage Execution
-
Fully Compatible
-
Execution Team 2024-11-11
In a concurrency fsm workload test, the workload itself sets up a collection and provides it to the test to use. In the case of sharded concurrency suites, the test setup may also shard the collection. However, some of these tests cannot use the provided collection because they require a collection with certain non-default options. Thus, they manually create a collection themselves as a part of the test-defined setup. One prominent case of this is time-series collections. In these cases, this causes the collection used by the test to not actually be sharded. We should make it so that test-defined collections get sharded as well, so that we get proper test coverage.
- is related to
-
SERVER-96700 timeseries_upserts.js fails when using a sharded collection
- Open
-
SERVER-96699 fle2_compact.js fails when using a sharded collection
- In Code Review
- related to
-
SERVER-89825 Investigate why jstests/concurrency/fsm_workloads/timeseries_mirrored_writes.js fails in case of concurrent moveCollection
- Closed
-
SERVER-95067 Time-series inserts can generate multiple batches referencing the same bucket
- Closed