[SERVER-76106] Acquire the DDL lock over the target database on renameCollection Created: 14/Apr/23  Updated: 29/Oct/23  Resolved: 08/May/23

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

Type: Bug 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
Assigned Teams:
Sharding EMEA
Backwards Compatibility: Fully Compatible
Sprint: Sharding EMEA 2023-05-01, Sharding EMEA 2023-05-15
Participants:
Linked BF Score: 10

 Description   

Currently, we are not acquiring the target database DDL lock on a renameCollection operation when the source DB differs from the target DB.

We should take it to serialize the renameCollection operation with any other DDL operation acting over the targeted database.



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

Author:

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

Message: SERVER-76106 Acquire the DDL lock over the target database on renameCollection
Branch: master
https://github.com/mongodb/mongo/commit/3c503e54d3b8a92600c343c10ab0747d6fd64b6d

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