Project

General

Profile

Actions
Copy link

Bug #17778

closed

table nodes contains on entry per node per generation, which is too much

Added by Nicolas CHARLES over 4 years ago. Updated over 4 years ago.

Status:
Released
Priority:
N/A
Assignee:
François ARMAND
Category:
Performance and scalability
Target version:
5.0.18
Pull Request:
https://github.com/Normation/rudder/p...
Severity:
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
To do
Fix check:
Checked
Regression:

Description

table nodes should historize nodes info, and it check changes at each policy generation
but it should not create a new entry for each node at each policy generation, as seem to indicate https://issues.rudder.io/issues/17772 , but rather create an entry when there's a change

On load test system, I have 74 971 809 entries in nodes, for 4500 fairly static nodes

Related issues 3 (0 open — 3 closed)

Related to Rudder - Question #17772: "nodes" table is very bigResolvedActions
Related to Rudder - Question #15436: How to clean the tables 'nodes' and 'nodes_info' of seemingly out of date informations ?ResolvedActions
Related to Rudder - Bug #14770: Invalid comparision of String and Option[String] in HistorizationService ReleasedNicolas CHARLESActions
Actions
Copy link
 #1

Updated by Nicolas CHARLES over 4 years ago

Actions
Copy link
 #2

Updated by Nicolas CHARLES over 4 years ago

  • Related to Question #15436: How to clean the tables 'nodes' and 'nodes_info' of seemingly out of date informations ? added
Actions
Copy link
 #3

Updated by Nicolas CHARLES over 4 years ago

this is most likely because we compare the description of the node from the DB (which is empty), with Some(description), which is some("")

Actions
Copy link
 #4

Updated by Nicolas CHARLES over 4 years ago

  • Status changed from New to In progress
  • Assignee set to Nicolas CHARLES
Actions
Copy link
 #5

Updated by Nicolas CHARLES over 4 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/3086
Actions
Copy link
 #6

Updated by Nicolas CHARLES over 4 years ago

  • Target version changed from 6.0.7 to 5.0.18

exists in 5.0, retargeting

Actions
Copy link
 #7

Updated by Nicolas CHARLES over 4 years ago

  • Pull Request changed from https://github.com/Normation/rudder/pull/3086 to https://github.com/Normation/rudder/pull/3088
Actions
Copy link
 #8

Updated by Nicolas CHARLES over 4 years ago

  • Related to Bug #14770: Invalid comparision of String and Option[String] in HistorizationService added
Actions
Copy link
 #9

Updated by Nicolas CHARLES over 4 years ago

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

Updated by François ARMAND over 4 years ago

  • Fix check changed from To do to Checked
Actions
Copy link
 #12

Updated by Vincent MEMBRÉ over 4 years ago

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 5.0.18 and 6.1.2 which were released today.

Actions
Copy link

Also available in: Atom PDF