[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: |
|
||||
| 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: |