-
Type: Task
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: Backlog
-
Component/s: Sharding
-
Fully Compatible
Currently drop_collection_sharded.js FSM workload is blacklisted in stepdown suites due to sveral bugs (see linked tickets). The goal of this ticket is to enable this test one all the known bugs are solved.
- 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-56560 Avoid thread scheduling deadlock in create collection coordinator
- Closed
-
SERVER-56561 create collection coordinator release critical section unconditionally on stepdown
- Closed
-
SERVER-56595 Create collection coordinator could fetch stale coll info from CSRS
- Closed
-
SERVER-56910 Skip Recoverable CS opObserver actions during recovery
- Closed
-
SERVER-56040 Changing the behavior of recoverable critical sections on secondary nodes
- Closed
-
SERVER-56559 Make drop collection FSM workload use multiple databases
- Closed
-
SERVER-56599 Make ShardingDDLCoordinatorService threadpool size unlimited
- Closed
- is depended on by
-
SERVER-56646 Enable drop_database_sharded.js FSM workload in stepdown suites
- Closed
-
SERVER-56789 Enable stepdown suites on sharded DDL FSM workloads
- Closed