Actions
Bug #26692
closed
Bug #26611: invalidateComplianceRequest get saturated with UpdateCompliance messages
Remove semaphore and use a sliding queue for compliance invalidation
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:
Checked
Regression:
No
Description
Our current implementation for the queue for compliance invalidation is strange. Clean it up without changing any logic but make it idiomatic.
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/6311
Updated by Anonymous about 1 month ago
- Status changed from Pending technical review to Pending release
Applied in changeset rudder|7b6e53fd3f4b8c9e6096ea84201973d6fbdf98c2.
Updated by François ARMAND 11 days ago
- Fix check changed from To do to Checked
Validated on load machine
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