Bug #15028
closed
Improve rsyslog performance by simplifying parsing of reports
Added by Nicolas CHARLES almost 6 years ago.
Updated almost 6 years ago.
Category:
Performance and scalability
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
- Related to Bug #14506: Improve 'rsyslog' to manage larger load of reports added
- Description updated (diff)
- Status changed from New to In progress
- Assignee set to Nicolas CHARLES
- 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
- Status changed from Pending technical review to Pending release
- Fix check changed from To do to Checked
- 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
- Status changed from Pending release to Released
This bug has been fixed in Rudder 5.0.12 which was released today.
Also available in: Atom
PDF