Actions
Bug #26725
open
Bug #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:
To do
Regression:
No
Description
Parent ticket #26692 lead to one CPU always loaded at 100%.
Reverting, the queue consumption strategy is not OK.
Updated by 
Updated by Anonymous
Actions