Actions
Bug #24712
closed
ExpiredCompliance events are pilling up
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:
To do
Fix check:
To do
Regression:
No
Description
There are objects ( com.normation.rudder.services.reports.CacheComplianceQueueAction$ExpiredCompliance ) piling up in the heap dump: there are roughly 1 million of com.normation.rudder.services.reports.CacheComplianceQueueAction$ExpiredCompliance piling up in 30 minutes
=> they don't seems to be consumed correctly, or perhaps produce too fast.
Updated by François ARMAND 18 days ago
- Related to Bug #24652: Rudder 8.1 slows down over time added
Updated by François ARMAND 18 days ago
- Related to Bug #24713: Dynamic groups are slow to compute in Rudder 8.1 added
Updated by François ARMAND 12 days ago
- Target version changed from 8.1.1 to 7.3.14
So, these problems exists since 7.3 actually (or even before).
Updated by François ARMAND 12 days ago
- Status changed from New to In progress
- Assignee set to François ARMAND
Updated by François ARMAND 12 days ago
- Status changed from In progress to Pending technical review
- Assignee changed from François ARMAND to Nicolas CHARLES
- Pull Request set to https://github.com/Normation/rudder/pull/5607
Updated by Anonymous 12 days ago
- Status changed from Pending technical review to Pending release
Applied in changeset rudder|bd0bd2aedbbafc481a3b5d705c83a876c44ac365.
Updated by Vincent MEMBRÉ 4 days ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder 7.3.14, 8.0.8 and 8.1.1 which were released today.
Actions