-
Type: New Feature
-
Resolution: Unresolved
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
Workload Scheduling
Deadlocks in the system shouldn't happen, but occasionally some bugs have come up where we end up deadlocked due to ticket exhaustion. The ticket holder monitor should be able to detect such a scenario by observing that one of the ticket pools is exhausted along with zero throughput. If such a scenario is detected, we can attempt to remediate it by increasing the ticket pool size. Potentially this may allow the system to make progress and resolve the deadlock. Note that this would primarily be a fallback mechanism and thus we should still make sure that in our testing we are made aware that a deadlock scenario was reached.