[SERVER-15725] profile commands appears to take out a G_X lock Created: 20/Oct/14  Updated: 20/Oct/14  Resolved: 20/Oct/14

Status: Closed
Project: Core Server
Component/s: Concurrency
Affects Version/s: 2.7.7
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Alvin Richards (Inactive) Assignee: Unassigned
Resolution: Done Votes: 0
Labels: 28qa
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Operating System: ALL
Participants:

 Description   

Problem:
See https://github.com/mongodb/mongo/blob/master/src/mongo/db/dbcommands.cpp#L351

            // Needs to be locked exclusively, because creates the system.profile collection
            // in the local database.
            //
            Lock::DBLock dbXLock(txn->lockState(), dbname, MODE_X);

Alternative:
Could this be scoped to a DB_X lock?



 Comments   
Comment by Alvin Richards (Inactive) [ 20/Oct/14 ]

My mistake - mis-read this, it is taking out a DB_X lock.

Generated at Thu Feb 08 03:38:47 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.