[SERVER-57032] Acquire only local distLock for Sharding DDL coordinators Created: 18/May/21  Updated: 06/Dec/22  Resolved: 25/Jun/21

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

Type: Task Priority: Major - P3
Reporter: Tommaso Tocci Assignee: [DO NOT USE] Backlog - Sharding EMEA
Resolution: Won't Fix Votes: 0
Labels: PM-1965-Cleanup
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-56654 Do not use the collection distributed... Closed
depends on SERVER-56779 Do not use the collection distributed... Closed
Related
related to SERVER-65891 Make all distLock acquisitions local-... Closed
Assigned Teams:
Sharding EMEA
Sprint: Sharding EMEA 2021-05-31
Participants:

 Description   

With the new implementation of the setFCV command (SERVER-55898) we have the guarantee that new and old DDL opeartions won't ever run concurrently on the cluster.
So there is no need anymore to take the distributed locks on this new paths, instead we will only use the local version of the distributed lock to serialize with other DDL operation running on the same shard.


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