[SERVER-78336] Take the collection DDL lock on metadataConsistency command running on collection level Created: 22/Jun/23 Updated: 29/Oct/23 Resolved: 10/Oct/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 7.2.0-rc0 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Silvia Surroca | Assignee: | Silvia Surroca |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | car-71-backport-declined, shardingemea-qw | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Sharding EMEA
|
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Sharding EMEA 2023-08-21, Sharding EMEA 2023-09-04, Sharding EMEA 2023-09-18, Sharding EMEA 2023-10-02, Sharding EMEA 2023-10-16 |
| Participants: | |
| Story Points: | 1 |
| Description |
|
Currently, the metadataConsistency command is always acquiring the database DDL lock in S mode. However, when the metadataConsistency command is running on the collection level, it would be better to take the database collection lock in IS mode and the collection DDL lock in S mode. With that improvement, we avoid blocking any DDL operation running over a collection that shares the same database that the collection we are running the metadataConsistency command on. |
| Comments |
| Comment by Githook User [ 09/Oct/23 ] |
|
Author: {'name': 'Silvia Surroca', 'email': 'silvia.surroca@mongodb.com', 'username': 'silviasuhu'}Message: |