Project

General

Profile

Actions

Bug #15035

closed

Avoid fetching nodeconfigurations twice when when runs processed

Added by Nicolas CHARLES almost 2 years ago. Updated almost 2 years 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 1 (0 open1 closed)

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

Updated by Nicolas CHARLES almost 2 years ago

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

Updated by Nicolas CHARLES almost 2 years ago

  • Status changed from New to In progress
Actions #3

Updated by Nicolas CHARLES almost 2 years 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
Actions #4

Updated by Nicolas CHARLES almost 2 years ago

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

Updated by Alexis MOUSSET almost 2 years ago

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

Updated by Vincent MEMBRÉ almost 2 years ago

  • Status changed from Pending release to Released

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

Actions

Also available in: Atom PDF