[SERVER-78600] No process to track when operations are set to non-default priority Created: 03/Jul/23  Updated: 25/Oct/23

Status: Backlog
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Major - P3
Reporter: Haley Connelly Assignee: Backlog - Storage Execution Team
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
Assigned Teams:
Storage Execution
Participants:

 Description   

Internal operations can now opt for a non-default priority via their AdmissionContext.

This ticket can serve as a placeholder for discussion:
(1) Would it be useful to track all new commits which change an operations default priority?
(2) What is the most practical approach?

The solution could be a simple as "won't do", adding some sort of commit hook/ list which tracks server tickets make operations opt out of default priority, etc.

A manual list could risk becoming stale quick, and as more operations utilize re-prioritisation, maybe we need a formal process.


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