[SERVER-54587] Make create collection resilient to stepdowns Created: 17/Feb/21  Updated: 29/Oct/23  Resolved: 29/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: Marcos José Grillo Ramirez Assignee: Marcos José Grillo Ramirez
Resolution: Fixed Votes: 0
Labels: PM-1965-Milestone-1
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-43899 Blacklist sharding_with_x509.js and s... Closed
depends on SERVER-53905 Implement PrimaryOnlyService for DDL ... Closed
depends on SERVER-55231 Stop using standalone shards in noPas... Closed
is depended on by SERVER-55551 Remove drop index from create collect... Closed
Duplicate
is duplicated by SERVER-33048 Add check to determine if idIndex req... Closed
Problem/Incident
causes SERVER-55616 Instances of ShardingDDLCoordinator a... Closed
Related
related to SERVER-55599 Add drop database FSM workload Closed
Backwards Compatibility: Fully Compatible
Sprint: Sharding 2021-03-08, Sharding 2021-03-22, Sharding 2021-04-05
Participants:

 Description   

Using the new resilient Primary Only Service implementation for DDL coordinators refactor the current create collection coordinator and add the necessary checkpoints to make the create collection resilient.



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

Author:

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

Message: SERVER-54587 Added resilience to the new create collection path
Branch: master
https://github.com/mongodb/mongo/commit/057657f0613e2fec34ac2e00b8d943ac05058896

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