Project

General

Profile

Actions

Bug #11919

closed

rudder agent check runs synchronously on all nodes, causing CPU spikes

Added by Alexis Mousset over 6 years ago. Updated over 4 years ago.

Status:
Rejected
Priority:
N/A
Assignee:
-
Category:
System techniques
Target version:
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)

Related issues 1 (0 open1 closed)

Related to Rudder - Bug #14258: Cron job checking rudder agent health, is ran every 5 minutes exactly, causing resource usage spikeReleasedNicolas CHARLESActions
Actions

Also available in: Atom PDF