[SERVER-81286] Investigate usages of exclusive locks in rename_collection.cpp Created: 20/Sep/23 Updated: 26/Oct/23 |
|
| Status: | Backlog |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Damian Wasilewicz | Assignee: | Backlog - Storage Execution Team |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | former-storex-namer, techdebt | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Storage Execution
|
||||||||
| Participants: | |||||||||
| Description |
|
There are more usages of Db Mode X (only renameCollectionForApplyOps, maybe not?) locks throughout the file, including in:
We should investigate whether Mode X locks should be taken here, particularly when they are taken on the DB level (like here for example)
|