Propose Enhancement for TimeoutHandler to Allow Scaling and Avoid DB Deadlocks

[ggrg]

Goal:

As a maintainer of the ML OSS codebase
I want to propose an enhanced processing of TimeoutHandler,
so that database deadlocks during performance testing are avoided and TimeoutHandler could be scaled

Tasks:

• Describe how current TimeoutHandler functions [@ggrg]
• Describe the disadvantages that might be causing the deadlocks [@ggrg]
• Plan how the TimeoutHandler might be enhanced [@ggrg]
• Prepare DB schema enhancement [@ggrg]
• Prepare sequence diagram(s) [@ggrg]
• Discuss and validate with the team [@ggrg]
• Resolve requests for changes and TODO items on the PRs

Acceptance Criteria:

• Designs are up-to date
• Migrations and seeds are provided

Pull Requests:

• feature/1089 Timeout Handler Enhancement central-ledger#515
• feature/1089 Timeout Handler Enhancement documentation#153

Follow-up:

• N/A

Dependencies:

• N/A

Accountability:

• Owner: TBC
• QA/Review: TBC