[SERVER-33694] The profile command should not take a MODE_X db lock at level 0 Created: 06/Mar/18  Updated: 06/Dec/22  Resolved: 06/Apr/18

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

Type: Improvement Priority: Major - P3
Reporter: James Wahlin Assignee: Backlog - Query Team (Inactive)
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Assigned Teams:
Query
Participants:

 Description   

At level 0 we are either setting the slowms or sampleRate global values which does not require a database lock or if the database exists, setting the profiling level to 0 which requires at most a MODE_S lock.

It is worth noting that Locker and RecoveryUnit stashing for transactions will block MODE_X acquisition on a participating database. This will make this issue more visible for those using transactions.


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