[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:
Documented
is documented by DOCS-15680 [Server] Add AdmissionContext::Priori... Closed
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: SERVER-72367 Only report admission priority if deprioritized
Branch: master
https://github.com/mongodb/mongo/commit/de67165e5c7a0124ec015b954d4931bdecb0bd61

Generated at Thu Feb 08 06:21:35 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.