-
Type: Improvement
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: None
-
Fully Compatible
-
v5.0, v4.4, v4.2
-
Execution Team 2021-06-14
-
(copied to CRM)
The profile command uses Shared and Exclusive locks to observe and change a database's profiling level, respectively.
These locks are extremely impactful and block read and write operations. Some services poll the profiling state once per minute. We should investigate how to stop taking such strong locks for this command.
- depends on
-
SERVER-47360 Should only take a collection MODE_IX lock for creating system.profile
- Closed
- is related to
-
SERVER-22541 Aggregation plan executors should be owned by global cursor manager
- Closed
-
SERVER-49102 Accept a filter expression as an alternative to slowMS/sampleRate
- Closed
-
SERVER-33889 Remove commands from embedded that shouldn't be available
- Closed
-
SERVER-21409 "profile" command with read-only option should not take exclusive database lock
- Closed
-
SERVER-47360 Should only take a collection MODE_IX lock for creating system.profile
- Closed
- related to
-
SERVER-51806 bulk key insertion phase of index build holds IX lock without yielding
- Closed