3b4136ff1e
* Added the new property 'execution_integrity_check_batch_size' under the [engine] group to limit the number of task executions that the integrity checker may process during one iteration. Closes-Bug: #1801876 Change-Id: I3c5074c45c476ebff109617cb15d56c54575dd4f
14 lines
713 B
YAML
14 lines
713 B
YAML
---
|
|
fixes:
|
|
- |
|
|
Workflow execution integrity checker mechanism was too agressive in case
|
|
of big workflows that have many task executions in RUNNING state at the
|
|
same time. The mechanism was selecting them all in one query and calling
|
|
"on_action_complete" for each of them within a single DB transaction.
|
|
That could lead to situations when this mechanism would totally block
|
|
all normal workflow processing whereas it should only be a "last chance"
|
|
aid in case of real infrastructure failures (e.g. MQ outage).
|
|
This issue has been fixed by adding a configurable batch size, so that
|
|
the checker can't select more than this number of task executions in
|
|
RUNNING state at once.
|