[SERVER-72367] Normal Operation Priority is exposed in CurOp and slow query logs Created: 22/Dec/22 Updated: 29/Oct/23 Resolved: 17/Jan/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 6.3.0-rc0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Haley Connelly | Assignee: | Jordi Olivares Provencio |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Storage Execution
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Sprint: | Execution Team 2023-01-23 | ||||||||
| Participants: | |||||||||
| Description |
|
Rather than exposing when operations take on the default priority (normal), or high priority (special case operations who ensure forward progress of the system), we should only show operation priority when operations are deprioritized |
| Comments |
| Comment by Githook User [ 17/Jan/23 ] |
|
Author: {'name': 'Jordi Olivares Provencio', 'email': 'jordi.olivares-provencio@mongodb.com', 'username': 'jordiolivares'}Message: |