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 #1

Updated by Alexis Mousset over 6 years ago

  • 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
Actions #3

Updated by Vincent MEMBRÉ over 6 years ago

  • Target version changed from 4.1.10 to 4.1.11
Actions #4

Updated by Vincent MEMBRÉ about 6 years ago

  • Target version changed from 4.1.11 to 4.1.12
  • Priority changed from 56 to 54
Actions #5

Updated by Vincent MEMBRÉ about 6 years ago

  • Target version changed from 4.1.12 to 4.1.13
  • Priority changed from 54 to 53
Actions #6

Updated by Benoît PECCATTE about 6 years ago

  • Target version changed from 4.1.13 to 411
Actions #7

Updated by Benoît PECCATTE about 6 years ago

  • Target version changed from 411 to 4.1.13
Actions #8

Updated by Vincent MEMBRÉ almost 6 years ago

  • Target version changed from 4.1.13 to 4.1.14
  • Priority changed from 53 to 52
Actions #9

Updated by Benoît PECCATTE almost 6 years ago

  • Target version changed from 4.1.14 to 4.1.15
  • Priority changed from 52 to 51
Actions #10

Updated by Vincent MEMBRÉ over 5 years ago

  • Target version changed from 4.1.15 to 4.1.16
  • Priority changed from 51 to 49
Actions #11

Updated by Vincent MEMBRÉ over 5 years ago

  • Target version changed from 4.1.16 to 4.1.17
Actions #12

Updated by Vincent MEMBRÉ over 5 years ago

  • Target version changed from 4.1.17 to 4.1.18
  • Priority changed from 49 to 48
Actions #13

Updated by Vincent MEMBRÉ over 5 years ago

  • Target version changed from 4.1.18 to 4.1.19
  • Priority changed from 48 to 47
Actions #14

Updated by Alexis Mousset over 5 years ago

  • Target version changed from 4.1.19 to 4.1.20
Actions #15

Updated by François ARMAND over 5 years ago

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

Updated by François ARMAND over 5 years ago

  • Target version changed from 4.1.20 to 4.1.21
Actions #17

Updated by Vincent MEMBRÉ about 5 years ago

  • Target version changed from 4.1.21 to 4.1.22
Actions #18

Updated by Vincent MEMBRÉ about 5 years ago

  • Target version changed from 4.1.22 to 4.1.23
Actions #19

Updated by Vincent MEMBRÉ about 5 years ago

  • Target version changed from 4.1.23 to 4.1.24
Actions #20

Updated by Vincent MEMBRÉ almost 5 years ago

  • Target version changed from 4.1.24 to 588
Actions #21

Updated by Alexis Mousset almost 5 years ago

  • Status changed from New to Rejected

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

Actions #22

Updated by Alexis Mousset over 4 years ago

  • Target version changed from 588 to 4.1.24
Actions

Also available in: Atom PDF