| 1 |
--- |
| 2 |
fixes: |
| 3 |
- | |
| 4 |
Action heartbeat checker was using scheduler to process expired action |
| 5 |
executions periodically. The side effect was that upon system reboot |
| 6 |
there may have been duplicating delayed calls in the database. So over |
| 7 |
time, the number of such calls could be significant and those jobs could |
| 8 |
even affect performance. This has now been fixed with regular threads |
| 9 |
without using scheduler at all. Additionally, the new configuration |
| 10 |
property "batch_size" has been added under the group "action_heartbeat" |
| 11 |
to control the maximum number of action executions processed during one |
| 12 |
iteration of the action execution heartbeat checker. |