-
Type: Task
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: None
-
None
-
Workload Scheduling
-
Fully Compatible
-
Workload Scheduling 2024-11-11, Workload Scheduling 2024-11-25
We shouldn't need TicketHolder to have the complex virtual interface it does today after the linked ticket to remove PriorityTickeTHolder is complete. At a minimum we should be able to remove the indirection around the queueing stats and consolidate the code implemented at the TicketHolder and SemaphoreTIcketHolder layers today.
One obstacle to consider is the MockTicketHolder used in the execution control unittests today. I suspect we can provide what this test needs without inheritance to fully simplify this interface into a single class/implementation, but if not we should still make it as minimal as possible.
- depends on
-
SERVER-96340 Remove PriorityTicketHolder
- Closed
- has to be done before
-
SERVER-96215 Implement max queue depth for server admission queues
- Closed
- is related to
-
SERVER-74082 Remove SemaphoreTicketHolder
- Closed