[SERVER-52813] No-stepdown concurrency suites for the new DDL paths Created: 12/Nov/20  Updated: 29/Oct/23  Resolved: 02/Mar/21

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: 4.9.0

Type: Task Priority: Major - P3
Reporter: Kaloian Manassiev Assignee: Marcos José Grillo Ramirez
Resolution: Fixed Votes: 0
Labels: PM-1965-Milestone-0
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-52758 Fit 'movePrimary' in the DDL coordina... Closed
depends on SERVER-52760 Implement a pseudo-coordinator for Re... Closed
depends on SERVER-52777 Fit 'refineShardKey' in the DDL coord... Closed
depends on SERVER-52779 Implement the new create/shard collec... Closed
depends on SERVER-52781 Implement the new rename collection p... Closed
depends on SERVER-52809 Implement the new drop collection pat... Closed
depends on SERVER-52811 Implement the new drop database path ... Closed
Problem/Incident
causes SERVER-54904 random_DDL_CRUD_operations.js is runn... Closed
causes SERVER-55248 CRUD state on FSM workload can fail i... Closed
Backwards Compatibility: Fully Compatible
Sprint: Sharding 2021-02-22, Sharding 2021-03-08
Participants:
Linked BF Score: 0

 Description   

This ticket is to implement a concurrency suite, which exercises the new DDL code paths and checks the objectives explained on the design document



 Comments   
Comment by Githook User [ 02/Mar/21 ]

Author:

{'name': 'Marcos José Grillo Ramirez', 'email': 'marcos.grillo@mongodb.com', 'username': 'm4nti5'}

Message: SERVER-52813 Add fsm workload for DDL and CRUD operations
Branch: master
https://github.com/mongodb/mongo/commit/f18d7ff55057815802fffba192af164972b4652a

Generated at Thu Feb 08 05:29:05 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.