[SERVER-74389] Investigate detecting when non-default priority operations added Created: 27/Feb/23 Updated: 28/Feb/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 | ||
| Assigned Teams: |
Storage Execution
|
| Participants: |
| Description |
|
By default, operations should be normal priority. Through SetAdmissionPriorityForLock RAII, internal operations can be changed to be low or immediate priority. It would be nice to have a linter detect when operations with non-default priority are added. In general, developers should reach out to the storage execution team before changing a priority. |