Evaluate if we have enough coverage for untracked unsharded collections in the config transition suites and add them.
This task is to specifically check if we have the coverage for unsharded collection that aren't tracked yet (because we haven't called moveCollection on them)
- is related to
-
SERVER-90628 _shardsvrReshardCollection command doesn't always get interrupted on stepdown
- Closed
-
SERVER-90697 Avoid running setFCV commands in jstestfuzz suites with config transitions
- Closed
-
SERVER-89826 Investigate errors related to moving capped collection that are part of multi-document transactions
- Closed
-
SERVER-90581 Add sharded_jscore_txns_with_config_transitions suite
- Closed
-
SERVER-90783 Add multi_shard_multi_stmt_txn_jscore_passthrough_with_config_transitions suite
- Closed
- related to
-
SERVER-96055 Add unsharded collection probability to concurrency_sharded_replication_with_balancer_and_config_transitions_and_add_remove_shard
- Backlog
-
SERVER-90876 Make movePrimaryFailIfNeedToCloneMovableCollections only allow movePrimary to move unsharded collections that are not movable by moveCollection
- Closed
-
SERVER-95248 Improve ContinuousAddRemoveShard's compatibility with FSM workloads
- Closed
-
SERVER-95333 Mark only FSM workloads that use a getMore outside of setup() / teardown() with "requires_getmore"
- Closed