[SERVER-76105] Allow sharding DDL operations to acquire DDL locks over multiple namespaces Created: 14/Apr/23  Updated: 29/Oct/23  Resolved: 19/May/23

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 7.1.0-rc0

Type: Task Priority: Major - P3
Reporter: Silvia Surroca Assignee: Silvia Surroca
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
is depended on by SERVER-75582 QE compact coordinator must acquire D... Closed
is depended on by SERVER-77016 QE cleanup coordinator must acquire D... Closed
Assigned Teams:
Sharding EMEA
Backwards Compatibility: Fully Compatible
Sprint: Sharding EMEA 2023-05-01, Sharding EMEA 2023-05-15, Sharding EMEA 2023-05-29
Participants:

 Description   

We need to add the ability to acquire the DDL locks ordered by name for Databases and Collections resources independently.

This is needed to prevent deadlocks on those DDL Coordinators that acquire more than one lock per database and/or collection (like renameCollection) once the ability to run concurrent DDL operations over the same database is enabled.



 Comments   
Comment by Githook User [ 19/May/23 ]

Author:

{'name': 'Silvia Surroca', 'email': 'silvia.surroca@mongodb.com', 'username': 'silviasuhu'}

Message: SERVER-76105 Allow sharding DDL operations to acquire DDL locks over multiple namespaces
Branch: master
https://github.com/mongodb/mongo/commit/bc57b7313bce890cf1a7d6cdf20f1ec25949698f

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