Project

General

Profile

Actions
Copy link

Bug #26692

closed

Bug #26611: invalidateComplianceRequest get saturated with UpdateCompliance messages

Remove semaphore and use a sliding queue for compliance invalidation

Bug #26692: Remove semaphore and use a sliding queue for compliance invalidation

Added by François ARMAND 8 months ago. Updated 7 months ago.

Status:
Released
Priority:
N/A
Assignee:
Vincent MEMBRÉ
Category:
Performance and scalability
Target version:
8.2.6
Pull Request:
https://github.com/Normation/rudder/p...
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.

Subtasks 2 (0 open — 2 closed)

Bug #26725: Reverting change in queue since it leads to CPU over useReleasedVincent MEMBRÉActions
Bug #26729: Remove semaphore and use a sliding queue for compliance invalidation (blocking version)ReleasedVincent MEMBRÉActions

Updated by François ARMAND 8 months ago Actions
Copy link
 #1

  • Status changed from New to In progress

Updated by François ARMAND 8 months ago Actions
Copy link
 #2

  • 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 8 months ago Actions
Copy link
 #3

  • Status changed from Pending technical review to Pending release

Updated by François ARMAND 8 months ago Actions
Copy link
 #4

  • Subtask #26725 added

Updated by François ARMAND 8 months ago Actions
Copy link
 #5

  • Fix check changed from To do to Checked

Validated on load machine

Updated by Vincent MEMBRÉ 7 months ago Actions
Copy link
 #6

  • 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
Copy link

Also available in: PDF Atom