Actions
Bug #11919
closedrudder agent check runs synchronously on all nodes, causing CPU spikes
Pull Request:
Severity:
Major - prevents use of part of Rudder | no simple workaround
UX impact:
User visibility:
Infrequent - complex configurations | third party integrations
Effort required:
Small
Priority:
47
Name check:
Fix check:
Regression:
Description
This can be a problem on nodes hosting a lot of VMs with Rudder for example, because the cf-promises check is quite cpu-intensive.
Currently the check script is run every 5 minutes in a cron job:
0,5,10,15,20,25,30,35,40,45,50,55 * * * *
We need to avoid this problem by:
- using the same frequency as the agent run
- start it at different times (using a kind of splay time like the regular agent)
Actions