Project

General

Profile

Bug #15117

Use a queue for "changes" cache update

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

Status:
Released
Priority:
N/A
Category:
Performance and scalability
Target version:
Severity:
User visibility:
Effort required:
Priority:
0

Description

We would like to use a queue of update for changes in place of futures to be able to accumulate requested update while one is processing, and then process all waiting in one go.


Related issues

Related to Rudder - Bug #15129: Queuing "changes" must be done in 5.1 ReleasedFrançois ARMANDActions
#1

Updated by François ARMAND 12 months ago

  • Status changed from New to In progress
#2

Updated by François ARMAND 12 months ago

  • Status changed from In progress to Pending technical review
  • Assignee changed from François ARMAND to Nicolas CHARLES
  • Pull Request set to https://github.com/Normation/rudder/pull/2282
#3

Updated by François ARMAND 11 months ago

  • Related to Bug #15129: Queuing "changes" must be done in 5.1 added
#5

Updated by François ARMAND 10 months ago

  • Status changed from Pending technical review to Pending release
#6

Updated by Vincent MEMBRÉ 7 months ago

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 6.0.0~beta1 which was released today.

Also available in: Atom PDF