Project

General

Profile

Actions

Bug #17778

closed

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

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

Status:
Released
Priority:
N/A
Category:
Performance and scalability
Target version:
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 (1 open2 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 ?NewActions
Related to Rudder - Bug #14770: Invalid comparision of String and Option[String] in HistorizationService ReleasedNicolas CHARLESActions
Actions

Also available in: Atom PDF