[SERVER-76130] ScopedAdmissionPriorityForLock Architecture Guide link is stale Created: 14/Apr/23 Updated: 29/Oct/23 Resolved: 03/May/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 7.1.0-rc0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Haley Connelly | Assignee: | Haley Connelly |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Execution Team 2023-05-01, Execution Team 2023-05-15 |
| Participants: |
| Description |
|
ScopedAdmissionPriorityForLock was originally called SetAdmissionPriorityForLock. The architecture guide text has the new name, but links to code with the old name. We should update this so developers aren't confused what to use when they want to deprioritize. We should also consider adding a sentence to detail that the "priority" can be seen in |
| Comments |
| Comment by Githook User [ 03/May/23 ] |
|
Author: {'name': 'Haley Connelly', 'email': 'haley.connelly@mongodb.com', 'username': 'haleyConnelly'}Message: |