[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:
Related
related to SERVER-72703 Downgrade $out's db lock to MODE_IX Closed
Assigned Teams:
Storage Execution
Participants:

 Description   

There are more usages of Db Mode X (only renameCollectionForApplyOps, maybe not?) locks throughout the file, including in:

  • renameTargetCollectionToTmp
  • renameCollectionWithinDB
  • renameCollectionWithinDBForApplyOps
  • renameCollectionAcrossDatabases
  • renameCollectionForApplyOps

We should investigate whether Mode X locks should be taken here, particularly when they are taken on the DB level (like here for example)

 

 


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