[SERVER-54915] The Sharding Routing Info Stability DistLock doesn't offer the assumed protection Created: 03/Mar/21  Updated: 29/Oct/23  Resolved: 03/Mar/21

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

Type: Bug Priority: Major - P3
Reporter: Kaloian Manassiev Assignee: Kaloian Manassiev
Resolution: Fixed Votes: 0
Labels: PM-1965-Milestone-0-Metadata-Format
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
is duplicated by SERVER-54787 Avoid ShardingRoutingInfoFormatStabil... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Sharding 2021-03-08
Participants:

 Description   

We added the Sharding Info Stability DistLock with the idea that it was going to serve as a barrier between DDL operations which use the old vs new metadata format. However, it doesn't actually provide the assumed protection, because even though two different shards could hold it, the first one to release it will release it for everyone.

Because of this we should remove it and implement a proper protection mechanism based on 2-Phase FCV or something similar.



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

Author:

{'name': 'Kaloian Manassiev', 'email': 'kaloian.manassiev@mongodb.com', 'username': 'kaloianm'}

Message: SERVER-54915 Remove the Sharding Routing Info Stability DistLock
Branch: master
https://github.com/mongodb/mongo/commit/c50fe3dc976e7beb1101bf353f3657a0e2b7152b

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