[SERVER-54807] Recover the metadata stability distlock on DDL coordinator step up Created: 26/Feb/21  Updated: 06/Dec/22  Resolved: 22/Mar/21

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

Type: Task Priority: Major - P3
Reporter: Jordi Serra Torrens Assignee: [DO NOT USE] Backlog - Sharding EMEA
Resolution: Won't Do Votes: 0
Labels: PM-1965-Milestone-1
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Assigned Teams:
Sharding EMEA
Participants:

 Description   

DDL operations are taking the 
ShardingRoutingInfoFormatStability on the shardsvr_* command (e.g. here for dropCollection) and then invoking the DDL coordinator In case of step down, when the new primary steps up and resumes the DDL operation, the ShardingRoutingInfoFormatStability won't be retaken.
This ticket is to ensure that we retake the ShardingRoutingInfoFormatStability on the DDL coordinator on step up.



 Comments   
Comment by Jordi Serra Torrens [ 22/Mar/21 ]

The ShardingRoutingInfoFormatStability distLock was removed on SERVER-54915 because it did not offer the assumed guarantees. Instead, SERVER-54918 will implement a 2-phase FCV barrier. Closing this ticket as Won't do.

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