Loading...

XML

Word

Printable

JSON

Type: Task
Resolution: Fixed
Priority: Major - P3
Fix Version/s: 5.0.0-rc0
Affects Version/s: None
Component/s: Sharding
Labels:
- PM-1965-Milestone-1

Backwards Compatibility:
Fully Compatible
Sprint:
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

(1 is related to)

Assignee:: Pierlauro Sciarelli

Reporter:: Marcos José Grillo Ramirez

Participants:: Githook User, Marcos José Grillo Ramirez, Pierlauro Sciarelli

Votes:: 0 Vote for this issue

Watchers:: 3 Start watching this issue

Created:: Mar 03 2021 11:22:38 AM UTC

Updated:: Oct 29 2023 09:56:48 PM UTC

Resolved:: May 11 2021 07:32:06 AM UTC