Project

General

Profile

Actions

Bug #11919

closed

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

Bug #11919: rudder agent check runs synchronously on all nodes, causing CPU spikes

Added by Alexis Mousset about 8 years ago. Updated about 6 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

Updated by Alexis Mousset about 8 years ago Actions #1

  • Severity set to Major - prevents use of part of Rudder | no simple workaround
  • User visibility set to Infrequent - complex configurations | third party integrations
  • Effort required set to Small
  • Priority changed from 0 to 56

Updated by Vincent MEMBRÉ almost 8 years ago Actions #3

  • Target version changed from 4.1.10 to 4.1.11

Updated by Vincent MEMBRÉ almost 8 years ago Actions #4

  • Target version changed from 4.1.11 to 4.1.12
  • Priority changed from 56 to 54

Updated by Vincent MEMBRÉ almost 8 years ago Actions #5

  • Target version changed from 4.1.12 to 4.1.13
  • Priority changed from 54 to 53

Updated by Benoît PECCATTE over 7 years ago Actions #6

  • Target version changed from 4.1.13 to 411

Updated by Benoît PECCATTE over 7 years ago Actions #7

  • Target version changed from 411 to 4.1.13

Updated by Vincent MEMBRÉ over 7 years ago Actions #8

  • Target version changed from 4.1.13 to 4.1.14
  • Priority changed from 53 to 52

Updated by Benoît PECCATTE over 7 years ago Actions #9

  • Target version changed from 4.1.14 to 4.1.15
  • Priority changed from 52 to 51

Updated by Vincent MEMBRÉ over 7 years ago Actions #10

  • Target version changed from 4.1.15 to 4.1.16
  • Priority changed from 51 to 49

Updated by Vincent MEMBRÉ over 7 years ago Actions #11

  • Target version changed from 4.1.16 to 4.1.17

Updated by Vincent MEMBRÉ about 7 years ago Actions #12

  • Target version changed from 4.1.17 to 4.1.18
  • Priority changed from 49 to 48

Updated by Vincent MEMBRÉ about 7 years ago Actions #13

  • Target version changed from 4.1.18 to 4.1.19
  • Priority changed from 48 to 47

Updated by Alexis Mousset about 7 years ago Actions #14

  • Target version changed from 4.1.19 to 4.1.20

Updated by François ARMAND about 7 years ago Actions #15

  • Related to Bug #14258: Cron job checking rudder agent health, is ran every 5 minutes exactly, causing resource usage spike added

Updated by François ARMAND almost 7 years ago Actions #16

  • Target version changed from 4.1.20 to 4.1.21

Updated by Vincent MEMBRÉ almost 7 years ago Actions #17

  • Target version changed from 4.1.21 to 4.1.22

Updated by Vincent MEMBRÉ almost 7 years ago Actions #18

  • Target version changed from 4.1.22 to 4.1.23

Updated by Vincent MEMBRÉ over 6 years ago Actions #19

  • Target version changed from 4.1.23 to 4.1.24

Updated by Vincent MEMBRÉ over 6 years ago Actions #20

  • Target version changed from 4.1.24 to 588

Updated by Alexis Mousset over 6 years ago Actions #21

  • Status changed from New to Rejected

We have added a random sleep before check in #14258, this should not occur anymore.

Updated by Alexis Mousset about 6 years ago Actions #22

  • Target version changed from 588 to 4.1.24
Actions

Also available in: PDF Atom