Project

General

Profile

Actions
Copy link

Bug #26729

closed

Bug #26611: invalidateComplianceRequest get saturated with UpdateCompliance messages

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

Bug #26725: Reverting change in queue since it leads to CPU over use

Remove semaphore and use a sliding queue for compliance invalidation (blocking version)

Added by François ARMAND about 1 month ago. Updated 2 days 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

Same as https://issues.rudder.io/issues/26692; but with a blocking queue.

Related issues 1 (0 open — 1 closed)

Related to Rudder - Bug #26464: Stackoverflow in NodeStatusReports event computingReleasedVincent MEMBRÉActions
Actions
Copy link
 #1

Updated by François ARMAND about 1 month ago

  • Status changed from New to In progress
Actions
Copy link
 #2

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/6318
Actions
Copy link
 #3

Updated by Anonymous 16 days ago

  • Status changed from Pending technical review to Pending release
Actions
Copy link
 #4

Updated by François ARMAND 11 days ago

  • Fix check changed from To do to Checked

Validated on load machine, the memory consumption is now OK.

Actions
Copy link
 #5

Updated by François ARMAND 11 days ago

  • Related to Bug #26464: Stackoverflow in NodeStatusReports event computing added
Actions
Copy link
 #6

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

Also available in: Atom PDF