Actions
Bug #26725
closedBug #26611: invalidateComplianceRequest get saturated with UpdateCompliance messages
Bug #26692: Remove semaphore and use a sliding queue for compliance invalidation
Reverting change in queue since it leads to CPU over use
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
To do
Fix check:
Checked
Regression:
No
Description
Parent ticket #26692 lead to one CPU always loaded at 100%.
Reverting, the queue consumption strategy is not OK.
Updated by François ARMAND about 1 month ago
- Status changed from New to In progress
Updated by François ARMAND about 1 month ago
- Status changed from In progress to Pending technical review
- Assignee changed from François ARMAND to Vincent MEMBRÉ
- Pull Request set to https://github.com/Normation/rudder/pull/6317
Updated by Anonymous about 1 month ago
- Status changed from Pending technical review to Pending release
Applied in changeset rudder|21f5a43efac014dc8a3bdecc9aef41db01b14bc6.
Updated by Vincent MEMBRÉ 2 days ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder 8.2.6 and 8.3.1 which were released today.
Actions