[SERVER-55034] The profile command should not take S or X database locks Created: 08/Mar/21 Updated: 29/Oct/23 Resolved: 08/Jun/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 4.4.7, 5.0.0-rc2, 5.1.0-rc0 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Louis Williams | Assignee: | Benety Goh |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | execution_intern, newgrad | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||||||||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||||||||||||||||||||||||||
| Backport Requested: |
v5.0, v4.4, v4.2
|
||||||||||||||||||||||||||||||||||||||||
| Sprint: | Execution Team 2021-06-14 | ||||||||||||||||||||||||||||||||||||||||
| Participants: | |||||||||||||||||||||||||||||||||||||||||
| Case: | (copied to CRM) | ||||||||||||||||||||||||||||||||||||||||
| Description |
|
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. |
| Comments |
| Comment by Githook User [ 17/Jun/21 ] |
|
Author: {'name': 'Benety Goh', 'email': 'benety@mongodb.com', 'username': 'benety'}Message: (cherry picked from commit 74fbf87121cd1d3c94dbaf5c4bed12456d2f1ccb) |
| Comment by Githook User [ 10/Jun/21 ] |
|
Author: {'name': 'Benety Goh', 'email': 'benety@mongodb.com', 'username': 'benety'}Message: (cherry picked from commit 74fbf87121cd1d3c94dbaf5c4bed12456d2f1ccb) |
| Comment by Githook User [ 08/Jun/21 ] |
|
Author: {'name': 'Benety Goh', 'email': 'benety@mongodb.com', 'username': 'benety'}Message: |
| Comment by Benety Goh [ 07/Jun/21 ] |
|
This is mostly a follow-up from |