[SERVER-70601] Separate TicketHolder management from TicketHolder logic Created: 17/Oct/22 Updated: 29/Oct/23 Resolved: 24/Oct/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 6.2.0-rc0 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Jordi Olivares Provencio | Assignee: | Haley Connelly |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | tech-debt | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||
| Sprint: | Execution Team 2022-10-31 | ||||||||||||
| Participants: | |||||||||||||
| Description |
|
Description Original Description The PriorityTicketHolder is currently a quite coupled pairing of implementation and scheduling policy. We want to move to a world where we can test different policies with ease. This should help improve testing and reasoning of the policy behaviour.
|
| Comments |
| Comment by Haley Connelly [ 24/Oct/22 ] |
|
Closing the work for this ticket. The original goal of separating policy from the ticketholder implementation has been moved to |
| Comment by Githook User [ 24/Oct/22 ] |
|
Author: {'name': 'Haley Connelly', 'email': 'haley.connelly@mongodb.com', 'username': 'haleyConnelly'}Message: |
| Comment by Jordi Olivares Provencio [ 17/Oct/22 ] |
|
haley.connelly@mongodb.com I've scheduled it for this sprint, but feel free to push it to the next one if necessary |