Loading...

XML

Word

Printable

JSON

Type: Task
Resolution: Done
Priority: Major - P3
Fix Version/s: None
Affects Version/s: None
Component/s: Catalog, Concurrency
Labels:
- car-investigation

Assigned Teams:

Catalog and Routing
Backwards Compatibility:
Fully Compatible
Sprint:
CAR Team 2025-05-12, CAR Team 2025-05-26, CAR Team 2025-06-09, CAR Team 2025-06-23, CAR Team 2025-07-07
Confidence Status:
None
Work Order:
3
CAR Domain/s:
None

Aha! Reference:
None
Tracking Level:
None
Risk Status:
None
Exec Notes:
None
Goal Name(s):
None
Goal Link:
None

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)

is related to

SERVER-103744 Deadlock between renameCollection, dbHash, and prepared transaction

Closed

SERVER-104410 Audit uses of database exclusive locks in DDL operations

Backlog

SERVER-106706 Use a DB IX lock for rename across databases

Backlog

SERVER-39518 Only use collection MODE_X locks for collection rename

Closed

related to

SERVER-72703 Downgrade $out's db lock to MODE_IX

Closed

Assignee:: Joan Bruguera Micó
Reporter:: Damian Wasilewicz
Participants:: Damian Wasilewicz, Joan Bruguera Micó, Pierlauro Sciarelli
Votes:: 0 Vote for this issue
Watchers:: 8 Start watching this issue

Created:: Sep 20 2023 09:22:45 PM UTC
Updated:: Jul 25 2025 05:22:04 PM UTC
Resolved:: Jun 25 2025 04:39:38 PM UTC
Confidence Status Last Update:: 21/May/25 1:54 PM