[SERVER-21409] "profile" command with read-only option should not take exclusive database lock Created: 11/Nov/15  Updated: 07/Jun/21  Resolved: 27/Jan/16

Status: Closed
Project: Core Server
Component/s: Diagnostics, Querying, Storage
Affects Version/s: None
Fix Version/s: 3.3.1

Type: Improvement Priority: Major - P3
Reporter: J Rassi Assignee: Benjamin Murphy
Resolution: Done Votes: 0
Labels: neweng
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-55034 The profile command should not take S... Closed
Backwards Compatibility: Fully Compatible
Sprint: Query F (02/01/16)
Participants:

 Description   

The "profile" command allows the user to either read or write the profiling level for the given database.

Currently, this command always takes an exclusive lock on the given database. Instead, the command should take a shared lock on the database if the user request is to simply read the database's current profiling level.



 Comments   
Comment by Githook User [ 27/Jan/16 ]

Author:

{u'username': u'benjaminmurphy', u'name': u'Benjamin Murphy', u'email': u'benjamin_murphy@me.com'}

Message: SERVER-21409 Read-only profile command takes only shared lock.

Closes #1063

Signed-off-by: Charlie Swanson <charlie.swanson@mongodb.com>
Branch: master
https://github.com/mongodb/mongo/commit/58f2842252bc833b3b051d46117d3f243ac2548f

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