Scale processing of "on-success", "on-error" and "on-complete"
Registered by
Oleg Ovcharuk
When it comes to processing big "on-success", "on-error" and "on-complete" clauses of direct Mistral workflows, Mistral doesn't scale it which leads to having one engine busy for a long time (sometimes ~ maximum duration of a DB transaction) while others not doing anything.
In order to fix this problem, we may try to use the state WAITING not only for "join" tasks but also for tasks that have been created but not processed yet (not created all inputs, actions etc.)
Blueprint information
- Status:
- Started
- Approver:
- Renat Akhmerov
- Priority:
- High
- Drafter:
- Oleg Ovcharuk
- Direction:
- Approved
- Assignee:
- Artem Lapin
- Definition:
- Approved
- Series goal:
- Accepted for ussuri
- Implementation:
- Needs Code Review
- Milestone target:
- wallaby-1
- Started by
- Renat Akhmerov
- Completed by
Related branches
Related bugs
Sprints
Whiteboard
Gerrit topic: https:/
Addressed by: https:/
WIP: scale "on-XXX" clauses
(?)