[SERVER-39518] Only use collection MODE_X locks for collection rename Created: 11/Feb/19  Updated: 29/Oct/23  Resolved: 29/Apr/19

Status: Closed
Project: Core Server
Component/s: Catalog, Index Maintenance, Storage
Affects Version/s: None
Fix Version/s: 4.1.11

Type: Improvement Priority: Major - P3
Reporter: Geert Bosch Assignee: Xiangyu Yao (Inactive)
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-39520 Only use collection MODE_X locks for ... Closed
Backwards Compatibility: Fully Compatible
Sprint: Storage NYC 2019-05-06
Participants:
Story Points: 8

 Description   

Ensure ordering in canonical ResourceId ordering of the collection locks to avoid deadlock.
Check that renaming a collection will not block on open transactions on different collections in the same database.



 Comments   
Comment by Githook User [ 29/Apr/19 ]

Author:

{'name': 'Xiangyu Yao', 'username': 'xy24', 'email': 'xiangyu.yao@mongodb.com'}

Message: SERVER-39518 Use database MODE_IX lock for rename collections
Branch: master
https://github.com/mongodb/mongo/commit/a318e73c733daf24e617303055f52b1810a17a98

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