-
Type: Task
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Sharding
-
Fully Compatible
-
Sharding EMEA 2021-05-17
- Since the does_not_support_stepdowns tag from the random_DDL_CRUD_operations.js FSM workload can't be removed (CRUDs are not retriable), create an FSM testing specifically subsequent DDL operations.
- Extend both of them to include a setFCV state.
The final objective must be to have the following FSMs:
- DDLs (create/rename/drop) [will support stepdown in SERVER-56789]
- DDLs + CRUD (no stepdown)
- DDLs + setFCV [will support stepdown in SERVER-56789]
- DDLs + setFCV + CRUD (no stepdown)
- depends on
-
SERVER-56390 Failed to construct ShardingDDLCoordinators do not get released
- Closed
-
SERVER-56482 create collection coordinator do not release critical section on stepdown
- Closed
-
SERVER-56556 create collection coordinator waits on wrong opTime to be mojority committed
- Closed
-
SERVER-55151 Implement rename participant primary only service
- Closed
- is depended on by
-
SERVER-56789 Enable stepdown suites on sharded DDL FSM workloads
- Closed
- is related to
-
SERVER-54850 Remove the concurrency_sharded_ddl_operations suite from evergreen
- Closed