Actions
Bug #15028
closed
Improve rsyslog performance by simplifying parsing of reports
Status:
Released
Priority:
N/A
Assignee:
Category:
Performance and scalability
Target version:
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
Reviewed
Fix check:
Checked
Regression:
Description
We are not using serials anymore for rules, yet we check them in the regexp of rsyslog in rudder server
With super high load (950k message in 8 minutes), it causes super high CPU usage, and saturates at 200% + CPU
not parsing them makes it stays below 200% rather above 200% cpu, with moments at 160% CPU
Updated by Nicolas CHARLES over 5 years ago
- Related to Bug #14506: Improve 'rsyslog' to manage larger load of reports added
Updated by Nicolas CHARLES over 5 years ago
- Status changed from New to In progress
- Assignee set to Nicolas CHARLES
Updated by Nicolas CHARLES over 5 years ago
- Status changed from In progress to Pending technical review
- Assignee changed from Nicolas CHARLES to Alexis Mousset
- Pull Request set to https://github.com/Normation/rudder-techniques/pull/1450
Updated by Nicolas CHARLES over 5 years ago
- Status changed from Pending technical review to Pending release
Applied in changeset rudder-techniques|dc7fdeac54b4bb53eaebef6ca33850a94fbffb02.
Updated by François ARMAND over 5 years ago
- Fix check changed from To do to Checked
Updated by Alexis Mousset over 5 years ago
- Subject changed from Improve 'rsyslog' configuration for insanely high load to Improve rsyslog performance by simplifying parsing of reports
- Name check changed from To do to Reviewed
Updated by Vincent MEMBRÉ over 5 years ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder 5.0.12 which was released today.
Actions