Project

General

Profile

Actions

Bug #4768

closed

check-rudder-agent should take splaytime into account when checking the last input update file

Added by Vincent MEMBRÉ about 10 years ago. Updated over 4 years ago.

Status:
Rejected
Priority:
2
Assignee:
-
Category:
System integration
Target version:
Severity:
Minor - inconvenience | misleading | easy workaround
UX impact:
User visibility:
Operational - other Techniques | Technique editor | Rudder settings
Effort required:
Priority:
0
Name check:
Fix check:
Regression:

Description

Following #4766, check-rudder-agent now takes into account the frequency of agent execution.

We decided to double the run interval so we could handle the splay time correctly and that we are sure that we haven't miss any execution.

But this case only occurs if the splaytime is very close to the frequency, otherwise the check is made really late and could have been done before:

if the frequency is every 2 hours, and the splaytime 5 minutes, if the agent  has ran a 0:00, next agent run can occurs between 2:00 and 2:05
If the lock happens here, it will only be detected at ~ 4:00, so have to wait at least 1h55 before fixing the issue.

The check should look every "run Interval + splaytime + 5 minutes" (to ensure that the agent has finished to run), so you have to wait only 5 minutes after splytime to fix tcdb issues.

To do that we need a file where the splaytime is stored, like the run interval.


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 Nicolas CHARLES about 10 years ago

The splay is constant for a given host, it's calculation is based on the FQ Host, IP address, and user id

If you schedule is every 2 hours, with a splay of 5 minutes, you will get (for instance), execution time of 0:04:36, 2:04:36, 4:04:36, etc
So you don't feed the splaytime to the script

The whole idea of having a doubled interval was to accept that one run could be very long, and the next one missed due to that. It may indeed not make a lot of sense when interval is long.

Actions #2

Updated by Nicolas CHARLES about 10 years ago

I guess here the real question is : when do we consider that a run is missed ? an interval + xx minutes ? an interval * a value ? something else ?

Actions #3

Updated by Nicolas CHARLES about 10 years ago

  • Status changed from New to Discussion
  • Assignee set to Jonathan CLARKE
Actions #4

Updated by Vincent MEMBRÉ about 10 years ago

  • Target version changed from 2.10.1 to 2.10.2
Actions #5

Updated by Jonathan CLARKE about 10 years ago

  • Target version changed from 2.10.2 to 2.10.3
Actions #6

Updated by Jonathan CLARKE almost 10 years ago

  • Target version changed from 2.10.3 to 2.10.4
Actions #7

Updated by Nicolas PERRON almost 10 years ago

  • Target version changed from 2.10.4 to 2.10.5
Actions #8

Updated by Vincent MEMBRÉ almost 10 years ago

  • Target version changed from 2.10.5 to 2.10.6
Actions #9

Updated by Matthieu CERDA over 9 years ago

  • Target version changed from 2.10.6 to 2.10.7
Actions #10

Updated by Vincent MEMBRÉ over 9 years ago

  • Target version changed from 2.10.7 to 2.10.8
Actions #11

Updated by Vincent MEMBRÉ over 9 years ago

  • Target version changed from 2.10.8 to 2.10.9
Actions #12

Updated by Vincent MEMBRÉ over 9 years ago

  • Target version changed from 2.10.9 to 2.10.10
Actions #13

Updated by Vincent MEMBRÉ over 9 years ago

  • Target version changed from 2.10.10 to 2.10.11
Actions #14

Updated by Vincent MEMBRÉ over 9 years ago

  • Target version changed from 2.10.11 to 2.10.12
Actions #15

Updated by Vincent MEMBRÉ over 9 years ago

  • Target version changed from 2.10.12 to 2.10.13
Actions #16

Updated by Vincent MEMBRÉ about 9 years ago

  • Target version changed from 2.10.13 to 2.10.14
Actions #17

Updated by Benoît PECCATTE about 9 years ago

  • Status changed from Discussion to New
  • Assignee deleted (Jonathan CLARKE)
Actions #18

Updated by Vincent MEMBRÉ about 9 years ago

  • Target version changed from 2.10.14 to 2.10.15
Actions #19

Updated by Vincent MEMBRÉ almost 9 years ago

  • Target version changed from 2.10.15 to 2.10.16
Actions #20

Updated by Vincent MEMBRÉ almost 9 years ago

  • Target version changed from 2.10.16 to 2.10.17
Actions #21

Updated by Vincent MEMBRÉ almost 9 years ago

  • Target version changed from 2.10.17 to 2.10.18
Actions #22

Updated by Vincent MEMBRÉ over 8 years ago

  • Target version changed from 2.10.18 to 2.10.19
Actions #23

Updated by Vincent MEMBRÉ over 8 years ago

  • Target version changed from 2.10.19 to 2.10.20
Actions #24

Updated by Vincent MEMBRÉ over 8 years ago

  • Target version changed from 2.10.20 to 277
Actions #25

Updated by Vincent MEMBRÉ over 8 years ago

  • Target version changed from 277 to 2.11.18
Actions #26

Updated by Vincent MEMBRÉ over 8 years ago

  • Target version changed from 2.11.18 to 2.11.19
Actions #27

Updated by Vincent MEMBRÉ over 8 years ago

  • Target version changed from 2.11.19 to 2.11.20
Actions #28

Updated by Vincent MEMBRÉ about 8 years ago

  • Target version changed from 2.11.20 to 2.11.21
Actions #29

Updated by Vincent MEMBRÉ about 8 years ago

  • Target version changed from 2.11.21 to 2.11.22
Actions #30

Updated by Vincent MEMBRÉ about 8 years ago

  • Target version changed from 2.11.22 to 2.11.23
Actions #31

Updated by Vincent MEMBRÉ almost 8 years ago

  • Target version changed from 2.11.23 to 2.11.24
Actions #32

Updated by Vincent MEMBRÉ almost 8 years ago

  • Target version changed from 2.11.24 to 308
Actions #33

Updated by Vincent MEMBRÉ almost 8 years ago

  • Target version changed from 308 to 3.1.14
Actions #34

Updated by Vincent MEMBRÉ over 7 years ago

  • Target version changed from 3.1.14 to 3.1.15
Actions #35

Updated by Vincent MEMBRÉ over 7 years ago

  • Target version changed from 3.1.15 to 3.1.16
Actions #36

Updated by Vincent MEMBRÉ over 7 years ago

  • Target version changed from 3.1.16 to 3.1.17
Actions #37

Updated by Vincent MEMBRÉ over 7 years ago

  • Target version changed from 3.1.17 to 3.1.18
Actions #38

Updated by Vincent MEMBRÉ over 7 years ago

  • Target version changed from 3.1.18 to 3.1.19
Actions #39

Updated by François ARMAND about 7 years ago

  • Severity set to Minor - inconvenience | misleading | easy workaround
  • User visibility set to Infrequent - complex configurations | third party integrations
  • Priority set to 0
Actions #40

Updated by Vincent MEMBRÉ about 7 years ago

  • Target version changed from 3.1.19 to 3.1.20
Actions #41

Updated by Vincent MEMBRÉ about 7 years ago

  • Target version changed from 3.1.20 to 3.1.21
Actions #42

Updated by François ARMAND about 7 years ago

  • User visibility changed from Infrequent - complex configurations | third party integrations to Operational - other Techniques | Technique editor | Rudder settings
  • Priority changed from 0 to 14
Actions #43

Updated by Vincent MEMBRÉ about 7 years ago

  • Target version changed from 3.1.21 to 3.1.22
Actions #44

Updated by Benoît PECCATTE almost 7 years ago

  • Priority changed from 14 to 28
Actions #45

Updated by Vincent MEMBRÉ almost 7 years ago

  • Target version changed from 3.1.22 to 3.1.23
Actions #46

Updated by Vincent MEMBRÉ almost 7 years ago

  • Target version changed from 3.1.23 to 3.1.24
Actions #47

Updated by Vincent MEMBRÉ over 6 years ago

  • Target version changed from 3.1.24 to 3.1.25
Actions #48

Updated by Benoît PECCATTE over 6 years ago

  • Priority changed from 28 to 29
Actions #49

Updated by Vincent MEMBRÉ over 6 years ago

  • Target version changed from 3.1.25 to 387
Actions #50

Updated by Vincent MEMBRÉ over 6 years ago

  • Target version changed from 387 to 4.1.10
Actions #51

Updated by Vincent MEMBRÉ over 6 years ago

  • Target version changed from 4.1.10 to 4.1.11
Actions #52

Updated by Vincent MEMBRÉ about 6 years ago

  • Target version changed from 4.1.11 to 4.1.12
  • Priority changed from 29 to 30
Actions #53

Updated by Vincent MEMBRÉ about 6 years ago

  • Target version changed from 4.1.12 to 4.1.13
Actions #54

Updated by Vincent MEMBRÉ almost 6 years ago

  • Target version changed from 4.1.13 to 4.1.14
Actions #55

Updated by Benoît PECCATTE almost 6 years ago

  • Target version changed from 4.1.14 to 4.1.15
  • Priority changed from 30 to 31
Actions #56

Updated by Vincent MEMBRÉ over 5 years ago

  • Target version changed from 4.1.15 to 4.1.16
Actions #57

Updated by Vincent MEMBRÉ over 5 years ago

  • Target version changed from 4.1.16 to 4.1.17
Actions #58

Updated by Vincent MEMBRÉ over 5 years ago

  • Target version changed from 4.1.17 to 4.1.18
  • Priority changed from 31 to 0
Actions #59

Updated by Vincent MEMBRÉ over 5 years ago

  • Target version changed from 4.1.18 to 4.1.19
Actions #60

Updated by Alexis Mousset over 5 years ago

  • Target version changed from 4.1.19 to 4.1.20
Actions #61

Updated by Nicolas CHARLES 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 #62

Updated by Alexis Mousset almost 5 years ago

  • Target version changed from 4.1.20 to 588
Actions #63

Updated by Nicolas CHARLES almost 5 years ago

  • Status changed from New to Rejected

rejecting, we don't need to take splaytime into account

Actions #64

Updated by Alexis Mousset over 4 years ago

  • Target version changed from 588 to 4.1.24
Actions

Also available in: Atom PDF