Project

General

Profile

Actions
Copy link

Bug #24649

closed

Rudder 8.1 doesn't start on large instance

Added by Nicolas CHARLES 8 months ago. Updated 8 months ago.

Status:
Released
Priority:
N/A
Assignee:
François ARMAND
Category:
Performance and scalability
Target version:
8.1.0~rc1
Pull Request:
https://github.com/Normation/rudder-p...
Severity:
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
To do
Fix check:
To do
Regression:
No

Description

Built in timeout in rudder-jetty & systemd is 120s
With 10 000 nodes, rudder needs more than 5 minutes to start

the init script needs to be changed as well as JETTY_START_TIMEOUT to 360 in /opt/rudder/etc/rudder-jetty.conf

Actions
Copy link
 #1

Updated by Vincent MEMBRÉ 8 months ago

  • Status changed from New to In progress
  • Assignee set to Vincent MEMBRÉ
Actions
Copy link
 #2

Updated by Vincent MEMBRÉ 8 months ago

  • Status changed from In progress to Pending technical review
  • Assignee changed from Vincent MEMBRÉ to François ARMAND
  • Pull Request set to https://github.com/Normation/rudder-packages/pull/2864
Actions
Copy link
 #3

Updated by Anonymous 8 months ago

  • Status changed from Pending technical review to Pending release
Actions
Copy link
 #4

Updated by Vincent MEMBRÉ 8 months ago

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 8.1.0~rc1 which was released today.

Actions
Copy link

Also available in: Atom PDF