[SERVER-47317] convertToCapped should not take MODE_X database locks Created: 03/Apr/20  Updated: 29/Oct/23  Resolved: 09/Apr/20

Status: Closed
Project: Core Server
Component/s: Concurrency, Storage
Affects Version/s: None
Fix Version/s: 4.4.0-rc1, 4.7.0

Type: Improvement Priority: Major - P3
Reporter: Geert Bosch Assignee: Gregory Noma
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Backwards Compatibility: Fully Compatible
Backport Requested:
v4.4
Sprint: Execution Team 2020-04-20
Participants:

 Description   

Currently it can block all operations to the database for the entire duration of the command. It should use MODE_X collection locks instead.



 Comments   
Comment by Githook User [ 10/Apr/20 ]

Author:

{'name': 'Gregory Noma', 'email': 'gregory.noma@gmail.com', 'username': 'gregorynoma'}

Message: SERVER-47317 Take collection MODE_X locks instead of database MODE_X lock in covertToCapped

(cherry picked from commit ff483e300c692dd2a47a649c4bddc3632178b2fd)
Branch: v4.4
https://github.com/mongodb/mongo/commit/9d4284a8010e35a640306017de895be568be4855

Comment by Githook User [ 09/Apr/20 ]

Author:

{'name': 'Gregory Noma', 'email': 'gregory.noma@gmail.com', 'username': 'gregorynoma'}

Message: SERVER-47317 Take collection MODE_X locks instead of database MODE_X lock in covertToCapped
Branch: master
https://github.com/mongodb/mongo/commit/ff483e300c692dd2a47a649c4bddc3632178b2fd

Generated at Thu Feb 08 05:13:50 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.