[SERVER-54787] Avoid ShardingRoutingInfoFormatStability serializing DDL operations on the same shard Created: 25/Feb/21  Updated: 06/Dec/22  Resolved: 03/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: Duplicate Votes: 0
Labels: PM-1965-Milestone-0
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates SERVER-54915 The Sharding Routing Info Stability D... Closed
Assigned Teams:
Sharding EMEA
Participants:

 Description   

Since SERVER-53092 we are using the "
ShardingRoutingInfoFormatStability" DistLock to ensure that DDL operations serialize with the patch up of metadata in the configsvr during FCV upgrade. This is to ensure DDL operations see a stable metadata format.
Currently, the DistLock serializes between shards and the configsvr or between threads on the same shard
For ShardingRoutingInfoFormatStability, we only wish to serialize between the configsvr and that shards, but not serialize DDL operations on the same shard.
For this, we could expose a "lockOnlyRemote" variant of the DistlockManager::lock that only serializes with the configsvr, and use it for the ShardingRoutingInfoFormatStability.


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