Project

General

Profile

Actions
Copy link

User story #4453

closed

User story #4451: Rudder agents run times should be splayed a maximum to ensure maximum scalability

Document splay time mechanism

Added by Jonathan CLARKE almost 11 years ago. Updated over 9 years ago.

Status:
Released
Priority:
3
Assignee:
Nicolas CHARLES
Category:
Documentation
Target version:
2.6.11
Pull Request:
https://github.com/Normation/rudder-d...
UX impact:
Suggestion strength:
User visibility:
Effort required:
Name check:
Fix check:
Regression:

Description

See #4451 for explanations. The doc doesn't explain this at all, adding a section for it.

Actions
Copy link
 #1

Updated by Jonathan CLARKE almost 11 years ago

  • Status changed from In progress to Pending technical review
  • Assignee changed from Jonathan CLARKE to Nicolas CHARLES
  • Pull Request set to https://github.com/Normation/rudder-doc/pull/51
Actions
Copy link
 #2

Updated by Jonathan CLARKE almost 11 years ago

  • Status changed from Pending technical review to Pending release
  • % Done changed from 0 to 100

Applied in changeset rudder-doc:commit:fd300567e59e3c73834f739d009470b041637a6f.

Actions
Copy link
 #3

Updated by Nicolas CHARLES almost 11 years ago

Applied in changeset rudder-doc:commit:06ebd65501aa0e8a966cabe77af3c9246f520f5d.

Actions
Copy link
 #4

Updated by Vincent MEMBRÉ almost 11 years ago

  • Status changed from Pending release to Released

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

Actions
Copy link
 #5

Updated by Benoît PECCATTE over 9 years ago

  • Tracker changed from 6 to User story
Actions
Copy link

Also available in: Atom PDF