[SERVER-75492] Optimize collection level path taking collection lock instead of db lock at checkMetadataConsistencyParticipant Created: 30/Mar/23 Updated: 29/Oct/23 Resolved: 26/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: | Pol Pinol | Assignee: | Pol Pinol |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | sharding-wfbf-day | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| 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 |
|
In case of collection level, there is no need to lock the database, we could simply need to lock the collection. The goal of this ticket is to optimize the path for checkMetadataConsistencyParticipant when the cmd is run at collection level. |
| Comments |
| Comment by Githook User [ 25/May/23 ] |
|
Author: {'name': 'Pol Pinol Castuera', 'email': 'pol.pinol@mongodb.com', 'username': 'PolPinol'}Message: |