Actions
Bug #15035
closed
Avoid fetching nodeconfigurations twice when when runs processed
Status:
Released
Priority:
N/A
Assignee:
Category:
Performance and scalability
Target version:
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
Reviewed
Fix check:
Error - Fixed
Regression:
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
Updated by Nicolas CHARLES almost 5 years ago
- Subject changed from Innefficient fetch of nodeconfigurations when runs are received to Inefficient fetch of nodeconfigurations when runs are received
Updated by Nicolas CHARLES almost 5 years ago
- Status changed from New to In progress
Updated by Nicolas CHARLES almost 5 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
Updated by Nicolas CHARLES almost 5 years ago
- Status changed from Pending technical review to Pending release
Applied in changeset rudder|6dc649ac8ac8cea0b774883f969fe8099017f2a9.
Updated by François ARMAND almost 5 years ago
- Fix check changed from To do to Checked
Updated by Alexis Mousset almost 5 years ago
- Subject changed from Inefficient fetch of nodeconfigurations when runs are received to Avoid fetching nodeconfigurations twice when when runs processed
- Name check changed from To do to Reviewed
Updated by Nicolas CHARLES almost 5 years ago
- Fix check changed from Checked to Error - Fixed
Updated by Vincent MEMBRÉ almost 5 years ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder 5.0.12 which was released today.
Actions