Loading...

XML

Word

Printable

JSON

Type: Improvement
Resolution: Fixed
Priority: Major - P3
Fix Version/s: 4.4.7, 5.0.0-rc2, 5.1.0-rc0
Affects Version/s: None
Component/s: None
Labels:
- execution_intern
- newgrad

Backwards Compatibility:
Fully Compatible
Backport Requested:

v5.0, v4.4, v4.2
Sprint:
Execution Team 2021-06-14
Case:
Confidence Status:
None
Work Order:
3

Aha! Reference:
None
Tracking Level:
None
Risk Status:
None
Exec Notes:
None
Goal Name:
None
Goal Link:
None

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

(1 is related to, 1 related to)

Assignee:: Benety Goh
Reporter:: Louis Williams
Participants:: Benety Goh, Githook User, Louis Williams
Votes:: 0 Vote for this issue
Watchers:: 7 Start watching this issue

Created:: Mar 08 2021 03:08:47 PM UTC
Updated:: Oct 29 2023 09:56:34 PM UTC
Resolved:: Jun 08 2021 06:21:26 PM UTC
Confidence Status Last Update:: 07/Jun/21 4:45 PM

Details

Description

Attachments

Issue Links

Activity

People

Dates