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.
Category:
Performance and scalability
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 to Question #15436: How to clean the tables 'nodes' and 'nodes_info' of seemingly out of date informations ? added
this is most likely because we compare the description of the node from the DB (which is empty), with Some(description), which is some("")
- Status changed from New to In progress
- Assignee set to Nicolas CHARLES
- 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
- Target version changed from 6.0.7 to 5.0.18
exists in 5.0, retargeting
- Pull Request changed from https://github.com/Normation/rudder/pull/3086 to https://github.com/Normation/rudder/pull/3088
- Related to Bug #14770: Invalid comparision of String and Option[String] in HistorizationService added
- Status changed from Pending technical review to Pending release
- Fix check changed from To do to Checked
- 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.
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by