[SERVER-68537] Yielding and restoring locks should persist the operation priority Created: 03/Aug/22 Updated: 07/Sep/22 Resolved: 07/Sep/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Haley Connelly | Assignee: | Leonardo Menti (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | PM-2935-Milestone1 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Sprint: | Execution Team 2022-09-05, Execution Team 2022-09-19 |
| Participants: |
| Description |
|
When an operation yields its locks, and then restores its lock state, we should keep track of the admission context which will have the operation priority to ensure the GlobalLock is acquired with the same priority as in the original request |
| Comments |
| Comment by Haley Connelly [ 07/Sep/22 ] |
|
By storing the AdmissionContext on the Locker, this should be done automatically |