Project

General

Profile

Bug #15035

Avoid fetching nodeconfigurations twice when when runs processed

Added by Nicolas CHARLES 3 months ago. Updated about 2 months ago.

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

Description

Where runs are received, we invalidate the compliance for these nodes, and fetch their reportExecutions, joined to the nodeconfigurations
Just after that, we fetch the nodeconfigurations for these nodes.

We could reuse these nodeconfiguration, it would ease the strain on the database, and use less memory


Subtasks

Bug #15130: New directives don't show up in rules compliance nor in node detailsReleasedFrançois ARMANDActions

Associated revisions

Revision 6dc649ac (diff)
Added by Nicolas CHARLES 3 months ago

Fixes #15035: Inefficient fetch of nodeconfigurations when runs are received

History

#1

Updated by Nicolas CHARLES 3 months ago

  • Subject changed from Innefficient fetch of nodeconfigurations when runs are received to Inefficient fetch of nodeconfigurations when runs are received
#2

Updated by Nicolas CHARLES 3 months ago

  • Status changed from New to In progress
#3

Updated by Nicolas CHARLES 3 months ago

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

Updated by Nicolas CHARLES 3 months ago

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

Updated by Alexis MOUSSET about 2 months ago

  • Subject changed from Inefficient fetch of nodeconfigurations when runs are received to Avoid fetching nodeconfigurations twice when when runs processed
#10

Updated by Vincent MEMBRÉ about 2 months ago

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 5.0.12 which was released today.

Also available in: Atom PDF