[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:
Gantt Dependency
Related
related to SERVER-70792 Separate scheduling policy from ticke... Closed
Backwards Compatibility: Fully Compatible
Sprint: Execution Team 2022-10-31
Participants:

 Description   

Description
Right now, the ReaderWriterTicketHolder conflates the concept of managing a pool of tickets versus multiple pools of tickets. The ReaderWriterTicketHolder could be removed to separate the TicketHolder management (management of multiple pools of tickets) from the TicketHolder class (distribution of a single pool of tickets)

Original Description
(work for this ticket has been moved to SERVER-70792)

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 SERVER-70792

Comment by Githook User [ 24/Oct/22 ]

Author:

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

Message: SERVER-70601 Separate TicketHolder management from TicketHolder logic
Branch: master
https://github.com/mongodb/mongo/commit/525334b580816f2320d9a518b7d9eff908678ce9

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

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