[SERVER-70792] Separate scheduling policy from ticketholder implementation Created: 24/Oct/22  Updated: 27/Oct/23  Resolved: 16/Jan/23

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: Haley Connelly
Resolution: Works as Designed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
is related to SERVER-70601 Separate TicketHolder management from... Closed
Sprint: Execution Team 2022-10-31, Execution Team 2022-11-14, Execution Team 2022-12-12, Execution Team 2022-11-28, Execution Team 2023-01-23
Participants:

 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 [ 16/Jan/23 ]

Closing for now as it is not necessary for the scope of the project.

Comment by Haley Connelly [ 24/Nov/22 ]

The remaining work of this ticket is blocked until decisions are made about acceptable latency distributions for the TicketHolders.

Additionally, concerns have come up as to whether additional separation can be done with a separate policy that does not have side effects, and only computes which queue to dequeue / enqueue.

Comment by Githook User [ 11/Nov/22 ]

Author:

{'name': 'Haley Connelly', 'email': 'haley.connelly@mongodb.com', 'username': 'haleyConnelly'}

Message: SERVER-70792 Separate Queue from PriorityTicketHolder
Branch: master
https://github.com/mongodb/mongo/commit/977cf573cb8e924390e6f9108a1f9d28caf02199

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