Project

General

Profile

Actions
Copy link

Bug #15117

closed

Use a queue for "changes" cache update

Added by François ARMAND almost 5 years ago. Updated over 4 years ago.

Status:
Released
Priority:
N/A
Assignee:
Nicolas CHARLES
Category:
Performance and scalability
Target version:
6.0.0~beta1
Pull Request:
https://github.com/Normation/rudder/p...
Severity:
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
Fix check:
Regression:

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 1 (0 open — 1 closed)

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

Updated by François ARMAND almost 5 years ago

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

Updated by François ARMAND almost 5 years 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
Actions
Copy link
 #3

Updated by François ARMAND almost 5 years ago

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

Updated by François ARMAND over 4 years ago

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

Updated by Vincent MEMBRÉ over 4 years ago

  • Status changed from Pending release to Released

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

Actions
Copy link

Also available in: Atom PDF