Project

General

Profile

Actions

User story #4451

closed

Rudder agents run times should be splayed a maximum to ensure maximum scalability

Added by Jonathan CLARKE over 10 years ago. Updated about 10 years ago.

Status:
Released
Priority:
3
Category:
Performance and scalability
Target version:
UX impact:
Suggestion strength:
User visibility:
Effort required:
Name check:
Fix check:
Regression:

Description

Currently, the agent execution schedule is to run every 5 minutes. The "splaytime" is set to 1 minute, which means that each agent will choose a random interval between -60 and +60 seconds and run at the planned time + the random interval. This means agents will actually run at any time between 10:04 and 10:06 and not at exactly 10:05 (for example).

This mechanism allows to "smooth" the load over the network (traffic) and on the server (max connections and simultaneous logs).

We should increase this to 2 minutes, to benefit from this at the maximum. Anything more than 2 minutes is not possible, because then intervals would overlap.


Subtasks 2 (0 open2 closed)

User story #4452: Change splaytime to 5 minutes to ensure maximum scalabilityReleasedNicolas CHARLES2014-02-07Actions
User story #4453: Document splay time mechanismReleasedNicolas CHARLES2014-02-07Actions
Actions #1

Updated by Jonathan CLARKE over 10 years ago

  • Status changed from 13 to 12

Actually, I had misunderstood the definition of splaytime, as described in https://cfengine.com/docs/3.5/reference-components-cfexecd.html#splaytime.

What it actually does is choose a maximum delay to pick a random delay in, that is used to wait after a specified time. So, if splay time is "2 minutes", the agent will run between 10:05 and 10:07.

Therefore, we can set splaytime up to 5 minutes, with no risk of overlap.

Actions #2

Updated by Jonathan CLARKE over 10 years ago

  • Status changed from 12 to Pending release
Actions #3

Updated by Vincent MEMBRÉ about 10 years ago

  • Category changed from System techniques to Performance and scalability
Actions #4

Updated by Vincent MEMBRÉ about 10 years ago

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 2.10.0~beta1, which was released today.
Check out:

The release announcement: http://www.rudder-project.org/pipermail/rudder-announce/2014-March/000084.html
The full ChangeLog: http://www.rudder-project.org/foswiki/bin/view/System/Documentation:ChangeLog210
Download information: https://www.rudder-project.org/site/get-rudder/downloads/
Actions

Also available in: Atom PDF