[SERVER-77545] Wrap DB DDL lock acquisition under a Collection DDL lock acquisition Created: 29/May/23  Updated: 22/Nov/23  Resolved: 03/Jul/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
depends on SERVER-69470 Remove featureFlagAlwaysCreateConfigT... Open
is depended on by SERVER-76848 [false alarm] $out does not ensure th... Closed
Duplicate
is duplicated by SERVER-76848 [false alarm] $out does not ensure th... Closed
is duplicated by SERVER-78497 Drop index may not consider a timeser... Closed
Backwards Compatibility: Fully Compatible
Sprint: Sharding EMEA 2023-06-26, Sharding EMEA 2023-07-10
Participants:

 Description   

Wrap DB DDL lock acquisition under a Collection DDL lock acquisition.

This can only be done after SERVER-69470 since we were not always taking Database DDL locks before taking Collection DDL locks before PM-2850, especially to avoid blocking DDL operations over an entire database.



 Comments   
Comment by Githook User [ 03/Jul/23 ]

Author:

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

Message: SERVER-77545 SERVER-77422 Change DDL lock mode acquisitions and wrap DB DDL lock under a Collection DDL lock
Branch: master
https://github.com/mongodb/mongo/commit/3b3d7b073a49f3f273328a8a2f13a023d5357928

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