[SERVER-54605] Make rename collection coordinator resilient to stepdowns Created: 18/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: 5.0.0-rc0

Type: Task Priority: Major - P3
Reporter: Pierlauro Sciarelli Assignee: Pierlauro Sciarelli
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-53905 Implement PrimaryOnlyService for DDL ... Closed
Duplicate
is duplicated by SERVER-54946 Make rename collection resilient to s... Closed
Problem/Incident
causes SERVER-55616 Instances of ShardingDDLCoordinator a... Closed
Backwards Compatibility: Fully Compatible
Sprint: Sharding 2021-03-22, Sharding 2021-04-05
Participants:

 Description   

Move the rename collection coordinator flow into a resilient DDL coordinator.



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

Author:

{'name': 'Pierlauro Sciarelli', 'email': 'pierlauro.sciarelli@mongodb.com', 'username': 'pierlauro'}

Message: SERVER-54605 Make rename collection coordinator resilient to stepdowns (Part 2)
Branch: master
https://github.com/mongodb/mongo/commit/a532eba3fdd36789b8451d70a0a707be46a71117

Comment by Githook User [ 26/Mar/21 ]

Author:

{'name': 'Pierlauro Sciarelli', 'email': 'pierlauro.sciarelli@mongodb.com', 'username': 'pierlauro'}

Message: SERVER-54605 Make rename collection coordinator resilient to stepdowns (Part 1)
Branch: master
https://github.com/mongodb/mongo/commit/52ae7dc57616085c8e53a4d1dbc18b90531d3d6b

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